From: Stefan Hajnoczi <stefanha@redhat.com>
To: Cindy Lu <lulu@redhat.com>
Cc: mst@redhat.com, jasowang@redhat.com, dgilbert@redhat.com,
qemu-devel@nongnu.org, arei.gonglei@huawei.com,
kraxel@redhat.com, marcandre.lureau@redhat.com
Subject: Re: [PATCH v10 00/10]vhost-vdpa: add support for configure interrupt
Date: Mon, 8 Nov 2021 10:53:04 +0000 [thread overview]
Message-ID: <YYkBkGdlpeer18e9@stefanha-x1.localdomain> (raw)
In-Reply-To: <20211104164827.21911-1-lulu@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]
On Fri, Nov 05, 2021 at 12:48:17AM +0800, Cindy Lu wrote:
> these patches add the support for configure interrupt
>
> These codes are all tested in vp-vdpa (support configure interrupt)
> vdpa_sim (not support configure interrupt), virtio tap device
>
> test in virtio-pci bus and virtio-mmio bus
Hi,
vhost-user has a configuration space change notification but it uses a
slave channel message (VHOST_USER_SLAVE_CONFIG_CHANGE_MSG) instead of an
eventfd. Ideally the vhost kernel ioctl and vhost-user interfaces would
follow the same design.
I'm concerned "common" vhost code is going to end up with lots of
callbacks that are not available uniformly across vhost kernel, vdpa,
and vhost-user. That makes it hard to understand and debug vhost, plus
differences make it harder to to correctly extend these interfaces in
the future.
Is the decision to a new eventfd-based interface instead of
vhost_chr_read/write() deliberate?
If yes, do you think VHOST_USER_SLAVE_CONFIG_CHANGE_MSG was a design
mistake in vhost-user that needs to be fixed?
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 484 bytes --]
next prev parent reply other threads:[~2021-11-08 10:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 16:48 [PATCH v10 00/10]vhost-vdpa: add support for configure interrupt Cindy Lu
2021-11-04 16:48 ` [PATCH v10 01/10] virtio: introduce macro IRTIO_CONFIG_IRQ_IDX Cindy Lu
2021-11-04 16:48 ` [PATCH v10 02/10] virtio-pci: decouple notifier from interrupt process Cindy Lu
2021-11-04 16:48 ` [PATCH v10 03/10] virtio-pci: decouple the single vector from the " Cindy Lu
2021-11-04 16:48 ` [PATCH v10 04/10] vhost: introduce new VhostOps vhost_set_config_call Cindy Lu
2021-11-04 16:48 ` [PATCH v10 05/10] vhost-vdpa: add support for config interrupt Cindy Lu
2021-11-04 16:48 ` [PATCH v10 06/10] virtio: add support for configure interrupt Cindy Lu
2021-11-04 16:48 ` [PATCH v10 07/10] vhost: " Cindy Lu
2021-11-04 16:48 ` [PATCH v10 08/10] virtio-net: " Cindy Lu
2021-11-04 16:48 ` [PATCH v10 09/10] virtio-mmio: " Cindy Lu
2021-11-04 16:48 ` [PATCH v10 10/10] virtio-pci: " Cindy Lu
2021-11-07 8:36 ` [PATCH v10 00/10]vhost-vdpa: " Michael S. Tsirkin
2021-11-08 10:53 ` Stefan Hajnoczi [this message]
2021-11-11 4:41 ` Jason Wang
2021-11-11 9:21 ` Stefan Hajnoczi
2021-11-12 3:39 ` Jason Wang
2022-01-09 17:06 ` Michael S. Tsirkin
2022-01-09 17:56 ` Michael S. Tsirkin
2022-01-10 1:37 ` Cindy Lu
2022-01-10 2:37 ` Jason Wang
2022-01-10 2:40 ` Cindy Lu
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=YYkBkGdlpeer18e9@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=dgilbert@redhat.com \
--cc=jasowang@redhat.com \
--cc=kraxel@redhat.com \
--cc=lulu@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--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 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).