From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: slp@redhat.com, mathieu.poirier@linaro.org,
viresh.kumar@linaro.org, qemu-devel@nongnu.org,
stefanha@redhat.com, marcandre.lureau@redhat.com
Subject: Re: [PATCH v1 00/13] various virtio docs, fixes and tweaks
Date: Tue, 22 Mar 2022 15:50:28 +0000 [thread overview]
Message-ID: <87v8w656g3.fsf@linaro.org> (raw)
In-Reply-To: <20220322094901-mutt-send-email-mst@kernel.org>
"Michael S. Tsirkin" <mst@redhat.com> writes:
> On Mon, Mar 21, 2022 at 03:30:24PM +0000, Alex Bennée wrote:
>> Hi,
>>
>> This series is a sub-set of patches while I was trying to re-rev my
>> virtio-rpmb patches. It attempts to address a few things:
>>
>> - improve documentation for virtio/vhost/vhost-user
>> - document some of the API
>> - a hacky fix for F_CONFIG handling
>> - putting VhostUserState on a diet, make VhostUserHostNotifier dynamic
>
> So I think this is best deferred until after the release,
> more of a cleanup than a bugfix.
Sorry I should have made it clearer - I wasn't intending this for 7.0
but I also didn't want it bound up with the rpmb changes which will take
longer to land.
>
> I will tag this series, but please do remind me after the release
> to help make sure it does not get lost.
>
>
>> In particular I've been trying to better understand how vhost-user
>> interactions are meant to work and why there are two different methods
>> for instantiating them. If my supposition is correct perhaps a number
>> of devices that don't have in-kernel vhost equivalents could be converted?
>
> Hope I understand your question. Well we started off with saying
> vhost-user is just a backend, so should not affect the frontend device.
> This is clean and makes migration work e.g. you can migrate between
> different backends, but it makes adding features more work.
This is covered in the doc patch, specifically:
vhost_ops vs TYPE_VHOST_USER_BACKEND
>> While working onthe VhostUserHostNotifier changes I found it quite
>> hard to trigger the code. Is this rarely used code or just requires
>> backends we don't see in the testing?
>
> Which function are you asking about exactly?
vhost_user_slave_handle_vring_host_notifier
which is the only place where a mapping is set up AFAICT.
>
>> Alex Bennée (10):
>> hw/virtio: move virtio-pci.h into shared include space
>> virtio-pci: add notification trace points
>> hw/virtio: add vhost_user_[read|write] trace points
>> vhost-user.rst: add clarifying language about protocol negotiation
>> libvhost-user: expose vu_request_to_string
>> docs/devel: start documenting writing VirtIO devices
>> include/hw: start documenting the vhost API
>> contrib/vhost-user-blk: fix 32 bit build and enable
>> hw/virtio/vhost-user: don't suppress F_CONFIG when supported
>> virtio/vhost-user: dynamically assign VhostUserHostNotifiers
>>
>> Paolo Bonzini (3):
>> docs: vhost-user: clean up request/reply description
>> docs: vhost-user: rewrite section on ring state machine
>> docs: vhost-user: replace master/slave with front-end/back-end
>>
>> docs/devel/index-internals.rst | 1 +
>> docs/devel/virtio-backends.rst | 214 +++++++++
>> docs/interop/vhost-user-gpu.rst | 10 +-
>> docs/interop/vhost-user.rst | 555 ++++++++++++----------
>> meson.build | 2 +-
>> include/hw/virtio/vhost-user.h | 43 +-
>> include/hw/virtio/vhost.h | 132 ++++-
>> {hw => include/hw}/virtio/virtio-pci.h | 0
>> subprojects/libvhost-user/libvhost-user.h | 9 +
>> contrib/vhost-user-blk/vhost-user-blk.c | 6 +-
>> hw/scsi/vhost-user-scsi.c | 1 +
>> hw/virtio/vhost-scsi-pci.c | 2 +-
>> hw/virtio/vhost-user-blk-pci.c | 2 +-
>> hw/virtio/vhost-user-fs-pci.c | 2 +-
>> hw/virtio/vhost-user-i2c-pci.c | 2 +-
>> hw/virtio/vhost-user-input-pci.c | 2 +-
>> hw/virtio/vhost-user-rng-pci.c | 2 +-
>> hw/virtio/vhost-user-scsi-pci.c | 2 +-
>> hw/virtio/vhost-user-vsock-pci.c | 2 +-
>> hw/virtio/vhost-user.c | 133 ++++--
>> hw/virtio/vhost-vsock-pci.c | 2 +-
>> hw/virtio/virtio-9p-pci.c | 2 +-
>> hw/virtio/virtio-balloon-pci.c | 2 +-
>> hw/virtio/virtio-blk-pci.c | 2 +-
>> hw/virtio/virtio-input-host-pci.c | 2 +-
>> hw/virtio/virtio-input-pci.c | 2 +-
>> hw/virtio/virtio-iommu-pci.c | 2 +-
>> hw/virtio/virtio-net-pci.c | 2 +-
>> hw/virtio/virtio-pci.c | 5 +-
>> hw/virtio/virtio-rng-pci.c | 2 +-
>> hw/virtio/virtio-scsi-pci.c | 2 +-
>> hw/virtio/virtio-serial-pci.c | 2 +-
>> subprojects/libvhost-user/libvhost-user.c | 2 +-
>> contrib/vhost-user-blk/meson.build | 3 +-
>> hw/virtio/trace-events | 10 +-
>> 35 files changed, 831 insertions(+), 333 deletions(-)
>> create mode 100644 docs/devel/virtio-backends.rst
>> rename {hw => include/hw}/virtio/virtio-pci.h (100%)
>>
>> --
>> 2.30.2
--
Alex Bennée
next prev parent reply other threads:[~2022-03-22 15:56 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 15:30 [PATCH v1 00/13] various virtio docs, fixes and tweaks Alex Bennée
2022-03-21 15:30 ` [Virtio-fs] [PATCH v1 01/13] hw/virtio: move virtio-pci.h into shared include space Alex Bennée
2022-03-21 15:30 ` Alex Bennée
2022-03-21 22:27 ` [Virtio-fs] " Philippe Mathieu-Daudé
2022-03-21 22:27 ` Philippe Mathieu-Daudé
2022-03-21 15:30 ` [PATCH v1 02/13] virtio-pci: add notification trace points Alex Bennée
2022-03-21 15:30 ` [PATCH v1 03/13] hw/virtio: add vhost_user_[read|write] " Alex Bennée
2022-03-21 22:29 ` Philippe Mathieu-Daudé
2022-03-21 15:30 ` [PATCH v1 04/13] docs: vhost-user: clean up request/reply description Alex Bennée
2022-03-21 22:30 ` Philippe Mathieu-Daudé
2022-03-21 15:30 ` [PATCH v1 05/13] docs: vhost-user: rewrite section on ring state machine Alex Bennée
2022-03-21 15:30 ` [PATCH v1 06/13] docs: vhost-user: replace master/slave with front-end/back-end Alex Bennée
2022-03-21 15:30 ` [PATCH v1 07/13] vhost-user.rst: add clarifying language about protocol negotiation Alex Bennée
2022-03-21 15:30 ` [PATCH v1 08/13] libvhost-user: expose vu_request_to_string Alex Bennée
2022-03-21 22:31 ` Philippe Mathieu-Daudé
2022-03-21 15:30 ` [PATCH v1 09/13] docs/devel: start documenting writing VirtIO devices Alex Bennée
2022-03-21 15:30 ` [PATCH v1 10/13] include/hw: start documenting the vhost API Alex Bennée
2022-03-21 15:30 ` [PATCH v1 11/13] contrib/vhost-user-blk: fix 32 bit build and enable Alex Bennée
2022-03-21 22:32 ` Philippe Mathieu-Daudé
2022-05-16 10:46 ` Alex Bennée
2022-03-21 15:30 ` [PATCH v1 12/13] hw/virtio/vhost-user: don't suppress F_CONFIG when supported Alex Bennée
2022-03-22 14:02 ` Michael S. Tsirkin
2022-03-22 15:54 ` Alex Bennée
2022-03-22 16:22 ` Michael S. Tsirkin
2022-03-21 15:30 ` [PATCH v1 13/13] virtio/vhost-user: dynamically assign VhostUserHostNotifiers Alex Bennée
2022-12-06 10:54 ` Philippe Mathieu-Daudé
2022-12-06 15:45 ` Stefan Hajnoczi
2022-03-22 13:56 ` [PATCH v1 00/13] various virtio docs, fixes and tweaks Michael S. Tsirkin
2022-03-22 15:50 ` Alex Bennée [this message]
2022-03-22 16:13 ` Michael S. Tsirkin
2022-05-13 10:15 ` 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=87v8w656g3.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=marcandre.lureau@redhat.com \
--cc=mathieu.poirier@linaro.org \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=slp@redhat.com \
--cc=stefanha@redhat.com \
--cc=viresh.kumar@linaro.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.