From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: ronnie sahlberg <ronniesahlberg@gmail.com>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
Alex Williamson <alex.williamson@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] QEMU question: is eventfd not thread safe?
Date: Mon, 02 Jul 2012 10:45:15 +1000 [thread overview]
Message-ID: <1341189915.2588.12.camel@pasglop> (raw)
In-Reply-To: <CAN05THQAhguPHmHSAAJQUqw_kaj8Yw_r9scOYj65cqF61_2V0g@mail.gmail.com>
On Mon, 2012-07-02 at 10:42 +1000, ronnie sahlberg wrote:
>
> Would it be possible to change the set-event-handlers functions to
> automatically call qemu_notify_event() when the descriptos change?
> To eliminate the need to call this function at all ?
That definitely sounds like the right thing to do.
Cheers,
Ben.
next prev parent reply other threads:[~2012-07-02 0:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-01 11:06 [Qemu-devel] QEMU question: is eventfd not thread safe? Alexey Kardashevskiy
2012-07-01 12:43 ` Michael S. Tsirkin
2012-07-01 12:57 ` Alexey Kardashevskiy
2012-07-01 23:07 ` Benjamin Herrenschmidt
2012-07-02 0:06 ` Alexey Kardashevskiy
2012-07-02 0:42 ` ronnie sahlberg
2012-07-02 0:45 ` Benjamin Herrenschmidt [this message]
2012-07-02 0:44 ` Benjamin Herrenschmidt
2012-07-02 0:49 ` Benjamin Herrenschmidt
2012-07-01 22:30 ` Benjamin Herrenschmidt
2012-07-01 13:32 ` Paolo Bonzini
2012-07-01 13:40 ` Alexey Kardashevskiy
2012-07-01 14:46 ` Alexey Kardashevskiy
2012-07-01 15:03 ` Paolo Bonzini
2012-07-01 19:48 ` [Qemu-devel] [PATCH] eventfd: making it rhread safe Alexey Kardashevskiy
2012-07-09 3:10 ` Alexey Kardashevskiy
2012-07-18 8:25 ` Alexey Kardashevskiy
2012-07-18 11:47 ` Michael S. Tsirkin
2012-07-18 12:08 ` [Qemu-devel] [PATCH] eventfd: making it thread safe Alexey Kardashevskiy
2012-07-18 12:22 ` Michael S. Tsirkin
2012-07-18 12:58 ` Alexey Kardashevskiy
2012-07-18 12:52 ` Alexey Kardashevskiy
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=1341189915.2588.12.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.com \
/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).