From: Paolo Bonzini <pbonzini@redhat.com>
To: Avi Kivity <avi@redhat.com>,
anthony@codemonkey.ws, qemu-devel@nongnu.org,
Alexey Kardashevskiy <aik@ozlabs.ru>,
mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH] eventfd: making it thread safe
Date: Tue, 07 Aug 2012 08:25:49 +0200 [thread overview]
Message-ID: <5020B4ED.5090905@redhat.com> (raw)
In-Reply-To: <20120807040203.GM16664@truffala.fritz.box>
Il 07/08/2012 06:02, David Gibson ha scritto:
>> Perhaps it's better to do this unconditionally (on the delete path too)
>> so that removals are processed without delay and we don't have closed
>> fds hanging around in select().
>
> Well, I understand that Alexey discussed the patch with Paolo and
> Michael Tsirkin, and this was the preferred approach for now. Since
> obviously no events will happen on deleted fds, removing them from the
> select() is not really urgent.
Avi is not speaking about deleted fds, but about existing fds whose
handlers are temporarily removed. I don't see it as a blocker for
merging the patch because we've never observed it (and it's unlikely,
because temporary removal of handlers typically occurs from within a
handler, not from another thread).
Paolo
next prev parent reply other threads:[~2012-08-07 6:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 4:05 [Qemu-devel] [PATCH] eventfd: making it thread safe David Gibson
2012-08-06 14:05 ` Avi Kivity
2012-08-07 4:02 ` David Gibson
2012-08-07 6:25 ` Paolo Bonzini [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-08-22 3:01 David Gibson
2012-07-26 4:30 Alexey Kardashevskiy
2012-07-01 19:48 [Qemu-devel] [PATCH] eventfd: making it rhread safe Alexey Kardashevskiy
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=5020B4ED.5090905@redhat.com \
--to=pbonzini@redhat.com \
--cc=aik@ozlabs.ru \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=mst@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).