From: Jan Kiszka <jan.kiszka@siemens.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Avi Kivity <avi@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] event_notifier: move to top-level directory
Date: Tue, 27 Sep 2011 17:28:10 +0200 [thread overview]
Message-ID: <4E81EB8A.3070202@siemens.com> (raw)
In-Reply-To: <CAJSP0QWhQrLV4p3OEG9G-B11oM-PnLFH3K28xVcWPPnriKgGew@mail.gmail.com>
On 2011-09-27 17:17, Stefan Hajnoczi wrote:
> On Tue, Sep 27, 2011 at 3:26 PM, Avi Kivity <avi@redhat.com> wrote:
>> Has no business in hw/.
>>
>> Signed-off-by: Avi Kivity <avi@redhat.com>
>> ---
>> hw/event_notifier.c => event_notifier.c | 1 -
>> hw/event_notifier.h => event_notifier.h | 0
>> 2 files changed, 0 insertions(+), 1 deletions(-)
>> rename hw/event_notifier.c => event_notifier.c (98%)
>> rename hw/event_notifier.h => event_notifier.h (100%)
>
> Yay. Now perhaps we can kill qemu_eventfd(), whose users are
> typically poking around with write(2) and read(2) when really they
> could use the high-level event_notifier.h API.
EventNotifiers will have to be superseded by something more generic
first. It's not fully covering the use cases of cpus.c and
posix-aio-compat.c.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-09-27 15:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 14:26 [Qemu-devel] [PATCH] event_notifier: move to top-level directory Avi Kivity
2011-09-27 15:17 ` Stefan Hajnoczi
2011-09-27 15:28 ` Jan Kiszka [this message]
2011-09-27 16:05 ` Anthony Liguori
2011-09-27 16:39 ` Paolo Bonzini
2011-09-27 21:23 ` Anthony Liguori
2011-09-28 6:27 ` Paolo Bonzini
2011-09-28 7:52 ` Jan Kiszka
2011-09-28 8:00 ` Paolo Bonzini
2011-09-28 9:12 ` Stefan Hajnoczi
2011-11-01 22:18 ` Anthony Liguori
2011-11-02 18:10 ` Alexander Graf
2011-11-02 17:12 ` Avi Kivity
2011-11-02 17:13 ` Avi Kivity
2011-11-02 18:23 ` Alexander Graf
2011-11-02 17:22 ` Avi Kivity
2011-11-02 17:27 ` Alexander Graf
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=4E81EB8A.3070202@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=avi@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.