From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, stefanha@redhat.com
Subject: [PATCH 0/3] Cleanup CoQueue restart functions
Date: Wed, 27 Apr 2022 15:08:27 +0200 [thread overview]
Message-ID: <20220427130830.150180-1-pbonzini@redhat.com> (raw)
Sending this out now that NBD's incorrect uses have been fixed.
There is no equivalent of qemu_co_queue_enter_next that restarts all
coroutines but that is incorrect because qemu_co_queue_restart_all should
really be a coroutine_fn. The NBD uses have been fixed by removing the
calls to qemu_co_queue_restart_all; graphic_hw_update_done works just
because it uses the BQL; but the new rwlock for the BlockDriverState
graph will need it.
The series introduces the new function, removes some duplicated code
around it, and marks qemu_co_queue_next and qemu_co_queue_restart_all
as coroutine_fn.
Paolo
Paolo Bonzini (3):
coroutine-lock: qemu_co_queue_next is a coroutine-only
qemu_co_enter_next
coroutine-lock: introduce qemu_co_queue_enter_all
coroutine-lock: qemu_co_queue_restart_all is a coroutine-only
qemu_co_enter_all
block/io.c | 2 +-
include/qemu/coroutine.h | 27 +++++++++++++++++-----
ui/console.c | 2 +-
util/qemu-coroutine-lock.c | 47 +++++++++++++++-----------------------
4 files changed, 42 insertions(+), 36 deletions(-)
--
2.35.1
next reply other threads:[~2022-04-27 13:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 13:08 Paolo Bonzini [this message]
2022-04-27 13:08 ` [PATCH 1/3] coroutine-lock: qemu_co_queue_next is a coroutine-only qemu_co_enter_next Paolo Bonzini
2022-04-27 14:07 ` Eric Blake
2022-04-27 13:08 ` [PATCH 2/3] coroutine-lock: introduce qemu_co_queue_enter_all Paolo Bonzini
2022-04-27 14:12 ` Eric Blake
2022-04-27 13:08 ` [PATCH 3/3] coroutine-lock: qemu_co_queue_restart_all is a coroutine-only qemu_co_enter_all Paolo Bonzini
2022-04-27 14:21 ` Eric Blake
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=20220427130830.150180-1-pbonzini@redhat.com \
--to=pbonzini@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).