From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Fam Zheng <fam@euphon.net>, Paolo Bonzini <pbonzini@redhat.com>,
Julia Suvorova <jusual@redhat.com>,
qemu-block@nongnu.org, Cole Robinson <crobinso@redhat.com>
Subject: Re: [PATCH for-5.0] aio-posix: fix test-aio /aio/event/wait with fdmon-io_uring
Date: Fri, 3 Apr 2020 12:52:33 +0100 [thread overview]
Message-ID: <20200403115233.GB135040@stefanha-x1.localdomain> (raw)
In-Reply-To: <20200402145434.99349-1-stefanha@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]
On Thu, Apr 02, 2020 at 03:54:34PM +0100, Stefan Hajnoczi wrote:
> When a file descriptor becomes ready we must re-arm POLL_ADD. This is
> done by adding an sqe to the io_uring sq ring. The ->need_wait()
> function wasn't taking pending sqes into account and therefore
> io_uring_submit_and_wait() was not being called. Polling for cqes
> failed to detect fd readiness since we hadn't submitted the sqe to
> io_uring.
>
> This patch fixes the following tests/test-aio -p /aio/event/wait
> failure:
>
> ok 11 /aio/event/wait
> **
> ERROR:tests/test-aio.c:374:test_flush_event_notifier: assertion failed: (aio_poll(ctx, false))
>
> Reported-by: Cole Robinson <crobinso@redhat.com>
> Fixes: 73fd282e7b6dd4e4ea1c3bbb3d302c8db51e4ccf
> ("aio-posix: add io_uring fd monitoring implementation")
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> util/fdmon-io_uring.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-04-03 11:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 14:54 [PATCH for-5.0] aio-posix: fix test-aio /aio/event/wait with fdmon-io_uring Stefan Hajnoczi
2020-04-02 17:30 ` Cole Robinson
2020-04-03 7:26 ` Stefano Garzarella
2020-04-03 11:52 ` Stefan Hajnoczi [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=20200403115233.GB135040@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=crobinso@redhat.com \
--cc=fam@euphon.net \
--cc=jusual@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--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).