From: Jonathon Jongsma <jjongsma@redhat.com>
To: Stefano Garzarella <sgarzare@redhat.com>, 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>
Subject: Re: [PATCH v2 0/2] block/blkio: add 'fd' option to virtio-blk-vhost-vdpa driver
Date: Wed, 10 May 2023 11:02:52 -0500 [thread overview]
Message-ID: <600fa0d6-5c01-c8e9-54d4-6d2695e92015@redhat.com> (raw)
In-Reply-To: <20230504092843.62493-1-sgarzare@redhat.com>
On 5/4/23 4:28 AM, Stefano Garzarella wrote:
> 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(-)
>
I mentioned this briefly off-list, but I'm following up here just to
provide a bit more visibility. From libvirt's point of view, it is
actually much easier if we could pass the fd via the existing 'path'
parameter (using /dev/fdset/N as the path, for example) due to how we
construct the commandline for qemu. So if I get a vote, I would
definitely vote for that approach over adding a new 'fd' property.
Thanks,
Jonathon
next prev parent reply other threads:[~2023-05-10 16:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 9:28 [PATCH v2 0/2] block/blkio: add 'fd' option to virtio-blk-vhost-vdpa driver Stefano Garzarella
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 ` Jonathon Jongsma [this message]
2023-05-11 7:49 ` [PATCH v2 0/2] " 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=600fa0d6-5c01-c8e9-54d4-6d2695e92015@redhat.com \
--to=jjongsma@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--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).