qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: qemu-devel@nongnu.org
Cc: "Nicholas Piggin" <npiggin@gmail.com>,
	"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>,
	"Michael S . Tsirkin" <mst@redhat.com>
Subject: [RFC PATCH 0/2] async: rework async event API for replay
Date: Thu, 15 Aug 2024 23:28:35 +1000	[thread overview]
Message-ID: <20240815132838.615330-1-npiggin@gmail.com> (raw)

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

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



             reply	other threads:[~2024-08-15 13:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-15 13:28 Nicholas Piggin [this message]
2024-08-15 13:28 ` [RFC PATCH 1/2] async: rework async event API for replay 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 ` [RFC PATCH 0/2] async: rework async event API for replay Michael S. Tsirkin
2024-08-16  2:23   ` 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=20240815132838.615330-1-npiggin@gmail.com \
    --to=npiggin@gmail.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=mst@redhat.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 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).