From: "Michael S. Tsirkin" <mst@redhat.com>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: qemu-devel@nongnu.org,
"Pavel Dovgalyuk" <Pavel.Dovgalyuk@ispras.ru>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"John Snow" <jsnow@redhat.com>, "Cleber Rosa" <crosa@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>,
"Michael Tokarev" <mjt@tls.msk.ru>
Subject: Re: [RFC PATCH 0/2] async: rework async event API for replay
Date: Thu, 15 Aug 2024 11:30:40 -0400 [thread overview]
Message-ID: <20240815113029-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20240815132838.615330-1-npiggin@gmail.com>
On Thu, Aug 15, 2024 at 11:28:35PM +1000, Nicholas Piggin wrote:
> Continuing the conversation from the thread about record/replay
> virtio fix. Here is a sketch of how we could improve the naming
> convention so users of bh don't have to know about record/replay.
>
> Thanks,
> Nick
The API looks ok to me.
> Nicholas Piggin (2):
> async: rework async event API for replay
> async: add debugging assertions for record/replay in bh APIs
>
> docs/devel/replay.rst | 7 ++--
> include/block/aio.h | 35 +++++++++++++++--
> include/sysemu/replay.h | 2 +-
> block.c | 4 +-
> block/block-backend.c | 24 +++++++-----
> block/io.c | 5 ++-
> block/iscsi.c | 5 ++-
> block/nfs.c | 10 +++--
> block/null.c | 4 +-
> block/nvme.c | 8 ++--
> hw/ide/core.c | 7 ++--
> hw/scsi/scsi-bus.c | 6 +--
> monitor/monitor.c | 2 +-
> monitor/qmp.c | 5 ++-
> qapi/qmp-dispatch.c | 4 +-
> replay/replay-events.c | 25 ++++++------
> stubs/replay-tools.c | 2 +-
> util/aio-wait.c | 2 +-
> util/async.c | 63 ++++++++++++++++++++++++++++--
> util/main-loop.c | 2 +-
> util/thread-pool.c | 8 ++--
> scripts/block-coroutine-wrapper.py | 2 +-
> 22 files changed, 164 insertions(+), 68 deletions(-)
>
> --
> 2.45.2
next prev parent reply other threads:[~2024-08-15 15:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 13:28 [RFC PATCH 0/2] async: rework async event API for replay Nicholas Piggin
2024-08-15 13:28 ` [RFC PATCH 1/2] " Nicholas Piggin
2024-08-15 13:28 ` [RFC PATCH 2/2] async: add debugging assertions for record/replay in bh APIs Nicholas Piggin
2024-08-15 15:30 ` Michael S. Tsirkin [this message]
2024-08-16 2:23 ` [RFC PATCH 0/2] async: rework async event API for replay Nicholas Piggin
2024-08-16 7:34 ` Michael S. Tsirkin
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=20240815113029-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=Pavel.Dovgalyuk@ispras.ru \
--cc=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=jsnow@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=npiggin@gmail.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=wainersm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.