From: Stefano Garzarella <sgarzare@redhat.com>
To: qemu-devel@nongnu.org
Cc: Hanna Reitz <hreitz@redhat.com>,
qemu-block@nongnu.org, Eric Blake <eblake@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
jjongsma@redhat.com, Stefano Garzarella <sgarzare@redhat.com>
Subject: [PATCH v2 0/2] block/blkio: add 'fd' option to virtio-blk-vhost-vdpa driver
Date: Thu, 4 May 2023 11:28:41 +0200 [thread overview]
Message-ID: <20230504092843.62493-1-sgarzare@redhat.com> (raw)
v2:
- added patch 01 to use monitor_fd_param() in the blkio module
- use monitor_fd_param() to parse the fd like vhost devices [Stefan]
v1: https://lore.kernel.org/qemu-devel/20230502145050.224615-1-sgarzare@redhat.com/
The virtio-blk-vhost-vdpa driver in libblkio 1.3.0 supports the new
'fd' property. Let's expose this to the user, so the management layer
can pass the file descriptor of an already opened vhost-vdpa character
device. This is useful especially when the device can only be accessed
with certain privileges.
Stefano Garzarella (2):
stubs/monitor: add monitor_fd_param()
block/blkio: add 'fd' option to virtio-blk-vhost-vdpa driver
qapi/block-core.json | 6 ++++-
block/blkio.c | 53 +++++++++++++++++++++++++++++++++++++++++++-
stubs/monitor.c | 6 +++++
3 files changed, 63 insertions(+), 2 deletions(-)
--
2.40.1
next reply other threads:[~2023-05-04 9:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 9:28 Stefano Garzarella [this message]
2023-05-04 9:28 ` [PATCH v2 1/2] stubs/monitor: add monitor_fd_param() Stefano Garzarella
2023-05-04 9:28 ` [PATCH v2 2/2] block/blkio: add 'fd' option to virtio-blk-vhost-vdpa driver Stefano Garzarella
2023-05-10 16:02 ` [PATCH v2 0/2] " Jonathon Jongsma
2023-05-11 7:49 ` Stefano Garzarella
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=20230504092843.62493-1-sgarzare@redhat.com \
--to=sgarzare@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=hreitz@redhat.com \
--cc=jjongsma@redhat.com \
--cc=kwolf@redhat.com \
--cc=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).