From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Emanuele Giuseppe Esposito" <eesposit@redhat.com>,
armbru@redhat.com, "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Hanna Reitz" <hreitz@redhat.com>,
qemu-block@nongnu.org, "Fam Zheng" <fam@euphon.net>
Subject: Re: [PATCH v2 0/6] block: switch to AIO_WAIT_WHILE_UNLOCKED() where possible
Date: Tue, 14 Mar 2023 18:10:45 +0100 [thread overview]
Message-ID: <ZBCqlTExahQBniwy@redhat.com> (raw)
In-Reply-To: <20230309190855.414275-1-stefanha@redhat.com>
Am 09.03.2023 um 20:08 hat Stefan Hajnoczi geschrieben:
> v2:
> - Clarify NULL ctx argument in Patch 1 commit description [Kevin]
>
> AIO_WAIT_WHILE_UNLOCKED() is the future replacement for AIO_WAIT_WHILE(). Most
> callers haven't been converted yet because they rely on the AioContext lock. I
> looked through the code and found the easy cases that can be converted today.
Thanks, applied to block-next.
Kevin
prev parent reply other threads:[~2023-03-14 17:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 19:08 [PATCH v2 0/6] block: switch to AIO_WAIT_WHILE_UNLOCKED() where possible Stefan Hajnoczi
2023-03-09 19:08 ` [PATCH v2 1/6] block: don't acquire AioContext lock in bdrv_drain_all() Stefan Hajnoczi
2023-03-12 23:51 ` Wilfred Mallawa
2023-03-09 19:08 ` [PATCH v2 2/6] block: convert blk_exp_close_all_type() to AIO_WAIT_WHILE_UNLOCKED() Stefan Hajnoczi
2023-03-12 23:54 ` Wilfred Mallawa
2023-03-09 19:08 ` [PATCH v2 3/6] block: convert bdrv_graph_wrlock() " Stefan Hajnoczi
2023-03-12 23:57 ` Wilfred Mallawa
2023-03-09 19:08 ` [PATCH v2 4/6] block: convert bdrv_drain_all_begin() " Stefan Hajnoczi
2023-03-13 0:00 ` Wilfred Mallawa
2023-03-09 19:08 ` [PATCH v2 5/6] hmp: convert handle_hmp_command() " Stefan Hajnoczi
2023-03-13 0:02 ` Wilfred Mallawa
2023-03-09 19:08 ` [PATCH v2 6/6] monitor: convert monitor_cleanup() " Stefan Hajnoczi
2023-03-13 0:03 ` Wilfred Mallawa
2023-03-14 17:10 ` 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=ZBCqlTExahQBniwy@redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eesposit@redhat.com \
--cc=fam@euphon.net \
--cc=hreitz@redhat.com \
--cc=philmd@linaro.org \
--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).