From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [PATCH] iothread: defer AioContext GSource usage
Date: Mon, 10 Mar 2025 16:49:29 +0100 [thread overview]
Message-ID: <Z88KCdXK63a7nDIb@redhat.com> (raw)
In-Reply-To: <20250220040536.195180-1-stefanha@redhat.com>
Am 20.02.2025 um 05:05 hat Stefan Hajnoczi geschrieben:
> Getting the GSource for the AioContext stops fdmon-io_uring from working
> because it is not compatible with the glib event loop. Defer the GSource
> code until the glib event loop is actually used. For typical IOThreads
> this may never be the case and we can use fdmon-io_uring.
>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2025-03-10 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 4:05 [PATCH] iothread: defer AioContext GSource usage Stefan Hajnoczi
2025-03-10 15:49 ` Kevin Wolf [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=Z88KCdXK63a7nDIb@redhat.com \
--to=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).