qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Riku Voipio <riku.voipio@iki.fi>
To: Laurent Vivier <laurent@vivier.eu>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] linux-user: fix eventfd()
Date: Fri, 19 May 2017 13:34:17 +0000	[thread overview]
Message-ID: <20170519133417.GA18402@kos.to> (raw)
In-Reply-To: <260f8cca-719e-dc31-12cf-507e01270c53@vivier.eu>

On Tue, Apr 25, 2017 at 06:32:30PM +0200, Laurent Vivier wrote:
> Ping?

Applied, thanks. 

> Laurent
> 
> Le 01/03/2017 à 10:37, Laurent Vivier a écrit :
> > This patch series byte-swap the uint64_t data stream
> > of a file-descriptor opened with eventfd().
> > 
> > It allows to pass more LTP test cases:
> > 
> > eventfd01    1  TPASS  :  counter value matches required
> > eventfd01    2  TPASS  :  read failed with EAGAIN as expected
> > eventfd01    3  TPASS  :  counter value matches required
> > eventfd01    4  TPASS  :  write failed with EAGAIN as expected
> > eventfd01    5  TPASS  :  read failed with EINVAL as expected
> > eventfd01    6  TPASS  :  write failed with EINVAL as expected
> > eventfd01    7  TPASS  :  write failed with EINVAL as expected
> > eventfd01    8  TPASS  :  fd is set in readfds
> > eventfd01    9  TPASS  :  fd is not set in readfds
> > eventfd01   10  TPASS  :  fd is set in writefds
> > eventfd01   11  TPASS  :  fd is not set in writefds
> > eventfd01    1  TPASS  :  counter value matches required
> > eventfd01    2  TPASS  :  read failed with EAGAIN as expected
> > eventfd01    3  TPASS  :  counter value matches required
> > eventfd01    4  TPASS  :  write failed with EAGAIN as expected
> > eventfd01    5  TPASS  :  read failed with EINVAL as expected
> > eventfd01    6  TPASS  :  write failed with EINVAL as expected
> > eventfd01    7  TPASS  :  write failed with EINVAL as expected
> > eventfd01    8  TPASS  :  fd is set in readfds
> > eventfd01    9  TPASS  :  fd is not set in readfds
> > eventfd01   10  TPASS  :  fd is set in writefds
> > eventfd01   11  TPASS  :  fd is not set in writefds
> > eventfd01   12  TPASS  :  counter value write from child successful
> > eventfd01   13  TCONF  :  eventfd01.c:642: eventfd support is not available in AIO subsystem
> > eventfd01   14  TCONF  :  eventfd01.c:647: eventfd support is not available in AIO subsystem
> > eventfd01   15  TCONF  :  eventfd01.c:652: eventfd support is not available in AIO subsystem
> > 
> > Laurent Vivier (2):
> >   linux-user: call fd_trans_target_to_host_data() for write()
> >   linux-user: fix eventfd
> > 
> >  linux-user/syscall.c | 38 +++++++++++++++++++++++++++++++++++---
> >  1 file changed, 35 insertions(+), 3 deletions(-)
> > 
> 

      reply	other threads:[~2017-05-19 13:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01  9:37 [Qemu-devel] [PATCH 0/2] linux-user: fix eventfd() Laurent Vivier
2017-03-01  9:37 ` [Qemu-devel] [PATCH 1/2] linux-user: call fd_trans_target_to_host_data() for write() Laurent Vivier
2017-03-01  9:37 ` [Qemu-devel] [PATCH 2/2] linux-user: fix eventfd Laurent Vivier
2017-04-25 16:32 ` [Qemu-devel] [PATCH 0/2] linux-user: fix eventfd() Laurent Vivier
2017-05-19 13:34   ` Riku Voipio [this message]

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=20170519133417.GA18402@kos.to \
    --to=riku.voipio@iki.fi \
    --cc=laurent@vivier.eu \
    --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).