From: Fam Zheng <famz@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 3/4] exec: Notify cpu_register_map_client caller if the bounce buffer is available
Date: Mon, 16 Mar 2015 15:44:47 +0800 [thread overview]
Message-ID: <20150316074447.GD15098@ad.nay.redhat.com> (raw)
In-Reply-To: <55068793.8020005@redhat.com>
On Mon, 03/16 08:34, Paolo Bonzini wrote:
>
>
> On 16/03/2015 06:31, Fam Zheng wrote:
> > The caller's workflow is like
> >
> > if (!address_space_map()) {
> > ...
> > cpu_register_map_client();
> > }
> >
> > If bounce buffer became available after address_space_map() but before
> > cpu_register_map_client(), the caller could miss it and has to wait for the
> > next bounce buffer notify, which may never happen in the worse case.
> >
> > Just notify the list in cpu_register_map_client().
> >
> > Signed-off-by: Fam Zheng <famz@redhat.com>
> > ---
> > exec.c | 22 +++++++++++++++-------
> > 1 file changed, 15 insertions(+), 7 deletions(-)
> >
> > diff --git a/exec.c b/exec.c
> > index 3e54580..20381a0 100644
> > --- a/exec.c
> > +++ b/exec.c
> > @@ -2489,6 +2489,17 @@ QemuMutex map_client_list_lock;
> > static QLIST_HEAD(map_client_list, MapClient) map_client_list
> > = QLIST_HEAD_INITIALIZER(map_client_list);
> >
> > +static void cpu_notify_map_clients_unlocked(void)
> > +{
> > + MapClient *client;
> > +
> > + while (!QLIST_EMPTY(&map_client_list)) {
> > + client = QLIST_FIRST(&map_client_list);
> > + client->callback(client->opaque);
> > + cpu_unregister_map_client(client);
> > + }
> > +}
>
> Isn't the convention to call these functions "*_locked" (e.g.
> timer_mod_ns_locked, monitor_flush_locked, cpu_get_clock_locked)?
Exactly, will rename. Thanks.
Fam
>
> Otherwise okay.
>
> Paolo
>
> > +
> > void *cpu_register_map_client(void *opaque, void (*callback)(void *opaque))
> > {
> > MapClient *client = g_malloc(sizeof(*client));
> > @@ -2497,6 +2508,9 @@ void *cpu_register_map_client(void *opaque, void (*callback)(void *opaque))
> > client->opaque = opaque;
> > client->callback = callback;
> > QLIST_INSERT_HEAD(&map_client_list, client, link);
> > + if (!atomic_read(&bounce.in_use)) {
> > + cpu_notify_map_clients_unlocked();
> > + }
> > qemu_mutex_unlock(&map_client_list_lock);
> > return client;
> > }
> > @@ -2521,14 +2535,8 @@ static void cpu_unregister_map_client(void *_client)
> >
> > static void cpu_notify_map_clients(void)
> > {
> > - MapClient *client;
> > -
> > qemu_mutex_lock(&map_client_list_lock);
> > - while (!QLIST_EMPTY(&map_client_list)) {
> > - client = QLIST_FIRST(&map_client_list);
> > - client->callback(client->opaque);
> > - cpu_unregister_map_client(client);
> > - }
> > + cpu_notify_map_clients_unlocked();
> > qemu_mutex_unlock(&map_client_list_lock);
> > }
> >
> >
next prev parent reply other threads:[~2015-03-16 7:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 5:31 [Qemu-devel] [PATCH v3 0/4] exec: Make bounce buffer thread safe Fam Zheng
2015-03-16 5:31 ` [Qemu-devel] [PATCH v3 1/4] exec: Atomic access to bounce buffer Fam Zheng
2015-03-16 7:30 ` Paolo Bonzini
2015-03-16 7:42 ` Fam Zheng
2015-03-16 5:31 ` [Qemu-devel] [PATCH v3 2/4] exec: Protect map_client_list with mutex Fam Zheng
2015-03-16 7:33 ` Paolo Bonzini
2015-03-16 7:55 ` Fam Zheng
2015-03-16 5:31 ` [Qemu-devel] [PATCH v3 3/4] exec: Notify cpu_register_map_client caller if the bounce buffer is available Fam Zheng
2015-03-16 7:34 ` Paolo Bonzini
2015-03-16 7:44 ` Fam Zheng [this message]
2015-03-16 5:31 ` [Qemu-devel] [PATCH v3 4/4] dma-helpers: Fix race condition of continue_after_map_failure and dma_aio_cancel Fam Zheng
2015-03-16 7:36 ` Paolo Bonzini
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=20150316074447.GD15098@ad.nay.redhat.com \
--to=famz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).