RFC async: rework async event API for replay
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest2 patches 3 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | async: rework async event API for replayblock/ block/ block/ +9 more | +111 | 0 replies | |
| 2/2 | async: add debugging assertions for record/replay in bh APIsblock.c hw/ hw/ +10 more | +54 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC PATCH 0/2] async: rework async event API for replay
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(-)
Signature · 1 line
2.45.2