From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, Blue Swirl <blauwirbel@gmail.com>,
jan.kiszka@web.de, Paolo Bonzini <pbonzini@redhat.com>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH] Add compat eventfd header
Date: Wed, 29 Jun 2011 16:11:24 +0300 [thread overview]
Message-ID: <20110629131124.GA18283@redhat.com> (raw)
In-Reply-To: <823452D2-B620-40F2-8423-917947A0F3A3@suse.de>
On Wed, Jun 29, 2011 at 03:02:46PM +0200, Alexander Graf wrote:
>
> On 28.06.2011, at 17:35, Michael S. Tsirkin wrote:
>
> > Support build on RHEL 5.X where we have syscall for eventfd but not
> > userspace wrapper.
> >
> > (cherry-picked from commit 9e3269181e9bc56feb43bcd4e8ce0b82cd543e65
> > in qemu-kvm.git).
> >
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > ---
> > compat/sys/eventfd.h | 13 +++++++++++++
> > configure | 4 +++
> > 2 files changed, 16 insertions(+), 0 deletions(-)
> > create mode 100644 compat/sys/eventfd.h
> >
> > diff --git a/compat/sys/eventfd.h b/compat/sys/eventfd.h
> > new file mode 100644
> > index 0000000..f55d96a
> > --- /dev/null
> > +++ b/compat/sys/eventfd.h
> > @@ -0,0 +1,13 @@
> > +#ifndef _COMPAT_SYS_EVENTFD
> > +#define _COMPAT_SYS_EVENTFD
> > +
> > +#include <unistd.h>
> > +#include <syscall.h>
> > +
> > +
> > +static inline int eventfd (int count, int flags)
>
> coding style seems wrong.
What exactly? Two empty lines?
> However, I'm not sure I like the idea of adding this code in qemu. Wouldn't the RHEL5 libc be a better place for such a wrapper?
>
>
> Alex
My guess (I don't speak for red hat here) is that's unlikely to be
patched anytime soon. It helps me when I need to use such a box,
and the cost seems negligeable. What's the drawback?
--
MST
next prev parent reply other threads:[~2011-06-29 13:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 15:35 [Qemu-devel] [PATCH] Add compat eventfd header Michael S. Tsirkin
2011-06-29 13:02 ` Alexander Graf
2011-06-29 13:11 ` Michael S. Tsirkin [this message]
2011-06-29 13:22 ` Alexander Graf
2011-06-29 13:59 ` Michael S. Tsirkin
2011-06-29 14:07 ` Alexander Graf
2011-06-29 15:28 ` Michael S. Tsirkin
2011-06-29 15:30 ` Alexander Graf
2011-06-29 15:33 ` Michael S. Tsirkin
2011-06-29 15:52 ` 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=20110629131124.GA18283@redhat.com \
--to=mst@redhat.com \
--cc=agraf@suse.de \
--cc=aurelien@aurel32.net \
--cc=blauwirbel@gmail.com \
--cc=jan.kiszka@web.de \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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).