From: Kevin Wolf <kwolf@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [PATCH] block: split qemu/aio.h out of block/aio.h
Date: Tue, 2 Dec 2025 17:03:47 +0100 [thread overview]
Message-ID: <aS8N4_LDyW1DrF_x@redhat.com> (raw)
In-Reply-To: <20251128101555.227630-1-pbonzini@redhat.com>
Am 28.11.2025 um 11:15 hat Paolo Bonzini geschrieben:
> Rust bindings are roughly broken up according to subdirectories of
> include/ (that's not exact, but it's roughly an aim). However,
> block/aio.h contains both block layer-specific concepts (BlockAIOCB,
> BlockCompletionFunc) and AioContext-related declarations that are
> used be qemu/main-loop.h.
>
> Break out the latter into their own header file, and use that to
> break the inclusion of block/ from qemu/main-loop.h.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> Based on top of
> https://lore.kernel.org/qemu-devel/20251127131516.80807-3-pbonzini@redhat.com/
>
> include/block/aio.h | 838 +-------------------------------------
> include/qemu/aio.h | 852 +++++++++++++++++++++++++++++++++++++++
> include/qemu/main-loop.h | 4 +-
> 3 files changed, 857 insertions(+), 837 deletions(-)
> create mode 100644 include/qemu/aio.h
Is it really worth keeping a separate tiny include file for BlockAIOCB?
Maybe let's have a patch to move it and its three functions to
block-common.h, and then just move this file unchanged into the place
where it should always have been.
Kevin
next prev parent reply other threads:[~2025-12-02 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 10:15 [PATCH] block: split qemu/aio.h out of block/aio.h Paolo Bonzini
2025-11-28 13:14 ` Prasad Pandit
2025-12-02 7:42 ` Paolo Bonzini
2025-12-02 16:03 ` Kevin Wolf [this message]
2025-12-02 16:09 ` Paolo Bonzini
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=aS8N4_LDyW1DrF_x@redhat.com \
--to=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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.