xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Paul Durrant <xadimgnik@gmail.com>
To: "'Anthony PERARD'" <anthony.perard@citrix.com>
Cc: <xen-devel@lists.xenproject.org>, <qemu-devel@nongnu.org>,
	"'Paul Durrant'" <pdurrant@amazon.com>,
	"'Jerome Leseinne'" <jerome.leseinne@gmail.com>,
	"'Edwin Torok'" <edvin.torok@citrix.com>,
	"'Stefano Stabellini'" <sstabellini@kernel.org>
Subject: RE: [PATCH] xen-bus: reduce scope of backend watch
Date: Thu, 1 Oct 2020 09:03:25 +0100	[thread overview]
Message-ID: <008c01d697c9$579520a0$06bf61e0$@xen.org> (raw)
In-Reply-To: <20200930114235.GL2024@perard.uk.xensource.com>

> -----Original Message-----
> From: Anthony PERARD <anthony.perard@citrix.com>
> Sent: 30 September 2020 12:43
> To: Paul Durrant <paul@xen.org>
> Cc: xen-devel@lists.xenproject.org; qemu-devel@nongnu.org; Paul Durrant <pdurrant@amazon.com>; Jerome
> Leseinne <jerome.leseinne@gmail.com>; Edwin Torok <edvin.torok@citrix.com>; Stefano Stabellini
> <sstabellini@kernel.org>
> Subject: Re: [PATCH] xen-bus: reduce scope of backend watch
> 
> On Wed, Sep 23, 2020 at 04:57:31PM +0100, Paul Durrant wrote:
> > From: Paul Durrant <pdurrant@amazon.com>
> >
> > Currently a single watch on /local/domain/X/backend is registered by each
> > QEMU process running in service domain X (where X is usually 0). The purpose
> > of this watch is to ensure that QEMU is notified when the Xen toolstack
> > creates a new device backend area.
> > Such a backend area is specific to a single frontend area created for a
> > specific guest domain and, since each QEMU process is also created to service
> > a specfic guest domain, it is unnecessary and inefficient to notify all QEMU
> > processes.
> > Only the QEMU process associated with the same guest domain need
> > receive the notification. This patch re-factors the watch registration code
> > such that notifications are targetted appropriately.
> >
> > Reported-by: Jerome Leseinne <jerome.leseinne@gmail.com>
> > Signed-off-by: Paul Durrant <pdurrant@amazon.com>
> >
> > diff --git a/hw/xen/xen-backend.c b/hw/xen/xen-backend.c
> > index 10199fb58d..f2711fe4a7 100644
> > --- a/hw/xen/xen-backend.c
> > +++ b/hw/xen/xen-backend.c
> > @@ -41,6 +41,11 @@ static void xen_backend_table_add(XenBackendImpl *impl)
> >      g_hash_table_insert(xen_backend_table_get(), (void *)impl->type, impl);
> >  }
> >
> > +static void **xen_backend_table_keys(unsigned int *count)
> > +{
> > +    return g_hash_table_get_keys_as_array(xen_backend_table_get(), count);
> 
> That could be cast to (const gchar **) as the GLib doc suggest, or (const
> char **) since gchar and char are the same.
> https://developer.gnome.org/glib/stable/glib-Hash-Tables.html#g-hash-table-get-keys-as-array
> 

Ok, I'll re-arrange the const-ing to cast at the inner level.

> > +}
> > +
> >  static const XenBackendImpl *xen_backend_table_lookup(const char *type)
> >  {
> >      return g_hash_table_lookup(xen_backend_table_get(), type);
> > diff --git a/hw/xen/xen-bus.c b/hw/xen/xen-bus.c
> > index 9ce1c9540b..c83da93bf3 100644
> > --- a/hw/xen/xen-bus.c
> > +++ b/hw/xen/xen-bus.c
> > @@ -430,7 +430,13 @@ static void xen_bus_unrealize(BusState *bus)
> >      trace_xen_bus_unrealize();
> >
> >      if (xenbus->backend_watch) {
> > -        xen_bus_remove_watch(xenbus, xenbus->backend_watch, NULL);
> > +        unsigned int i;
> > +
> > +        for (i = 0; i < xenbus->backend_types; i++) {
> > +            xen_bus_remove_watch(xenbus, xenbus->backend_watch[i], NULL);
> 
> We should check if backend_watch[i] is NULL.
> 

Yes, I'll add a check.

> > +        }
> > +
> > +        g_free(xenbus->backend_watch);
> >          xenbus->backend_watch = NULL;
> >      }
> >
> 
> The rest of the patch looks fine. Next improvement is to only look at
> only one backend type in xen_bus_backend_changed() since there is now a
> watch per backend type :-), but that would be for another day.
> 

Might not be too tricky. I'll see if I can come up with a follow-up patch.

  Paul

> Cheers,
> 
> --
> Anthony PERARD



      reply	other threads:[~2020-10-01  8:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-23 15:57 [PATCH] xen-bus: reduce scope of backend watch Paul Durrant
2020-09-30 11:42 ` Anthony PERARD
2020-10-01  8:03   ` Paul Durrant [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='008c01d697c9$579520a0$06bf61e0$@xen.org' \
    --to=xadimgnik@gmail.com \
    --cc=anthony.perard@citrix.com \
    --cc=edvin.torok@citrix.com \
    --cc=jerome.leseinne@gmail.com \
    --cc=paul@xen.org \
    --cc=pdurrant@amazon.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).