From: Tiwei Bie <tiwei.bie@intel.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, virtio-dev@lists.oasis-open.org,
alex.williamson@redhat.com, jasowang@redhat.com,
pbonzini@redhat.com, stefanha@redhat.com,
cunming.liang@intel.com, dan.daly@intel.com,
jianfeng.tan@intel.com, zhihong.wang@intel.com,
xiao.w.wang@intel.com
Subject: Re: [Qemu-devel] [PATCH v2 3/6] virtio: support adding sub-regions for notify region
Date: Tue, 27 Mar 2018 21:47:05 +0800 [thread overview]
Message-ID: <20180327134705.3zqzangejm2yy3ph@debian> (raw)
In-Reply-To: <20180322164345-mutt-send-email-mst@kernel.org>
On Thu, Mar 22, 2018 at 04:57:23PM +0200, Michael S. Tsirkin wrote:
> On Mon, Mar 19, 2018 at 03:15:34PM +0800, Tiwei Bie wrote:
[...]
> > +
> > +bool virtio_pci_page_per_vq_enabled(VirtIODevice *vdev)
> > +{
> > + VirtIOPCIProxy *proxy = virtio_device_to_virtio_pci_proxy(vdev);
> > +
> > + if (proxy == NULL) {
> > + return false;
> > + }
> > +
> > + return !!(proxy->flags & VIRTIO_PCI_FLAG_PAGE_PER_VQ);
> > +}
> > +
>
> VIRTIO_PCI_FLAG_PAGE_PER_VQ is not something external users
> should care about. Need to find some other way to express the
> specific requirements.
>
> In particular do you want to use a host page per VQ?
>
> This isn't what VIRTIO_PCI_FLAG_PAGE_PER_VQ does - it uses a 4K offset
> which does not match a memory page size on all platforms.
Yeah, right. I'll think about how to deal with this.
>
>
> > +int virtio_pci_notify_region_map(VirtIODevice *vdev, int queue_idx,
> > + MemoryRegion *mr)
> > +{
> > + VirtIOPCIProxy *proxy = virtio_device_to_virtio_pci_proxy(vdev);
> > + int offset;
> > +
> > + if (proxy == NULL || !virtio_pci_modern(proxy)) {
> > + return -1;
> > + }
> > +
> > + offset = virtio_pci_queue_mem_mult(proxy) * queue_idx;
> > + memory_region_add_subregion(&proxy->notify.mr, offset, mr);
> > +
> > + return 0;
> > +}
> > +
> > +void virtio_pci_notify_region_unmap(VirtIODevice *vdev, MemoryRegion *mr)
> > +{
> > + VirtIOPCIProxy *proxy = virtio_device_to_virtio_pci_proxy(vdev);
> > +
> > + if (proxy != NULL) {
> > + memory_region_del_subregion(&proxy->notify.mr, mr);
> > + }
> > +}
> > +
> > static void virtio_pci_pre_plugged(DeviceState *d, Error **errp)
> > {
> > VirtIOPCIProxy *proxy = VIRTIO_PCI(d);
> > diff --git a/hw/virtio/virtio-pci.h b/hw/virtio/virtio-pci.h
> > index 813082b0d7..8061133741 100644
> > --- a/hw/virtio/virtio-pci.h
> > +++ b/hw/virtio/virtio-pci.h
> > @@ -213,6 +213,11 @@ static inline void virtio_pci_disable_modern(VirtIOPCIProxy *proxy)
> > proxy->disable_modern = true;
> > }
> >
> > +bool virtio_pci_page_per_vq_enabled(VirtIODevice *vdev);
> > +int virtio_pci_notify_region_map(VirtIODevice *vdev, int queue_idx,
> > + MemoryRegion *mr);
> > +void virtio_pci_notify_region_unmap(VirtIODevice *vdev, MemoryRegion *mr);
> > +
> > /*
> > * virtio-scsi-pci: This extends VirtioPCIProxy.
> > */
>
> These are not great APIs unfortunately. Need to come up with generic names.
> E.g. do we register and de-register host notifiers maybe?
>
I like the name "host notifier". I'll try to use it. Thanks a lot!
>
> > diff --git a/hw/virtio/virtio.c b/hw/virtio/virtio.c
> > index 006d3d1148..90ee72984c 100644
> > --- a/hw/virtio/virtio.c
> > +++ b/hw/virtio/virtio.c
> > @@ -22,6 +22,7 @@
> > #include "qemu/atomic.h"
> > #include "hw/virtio/virtio-bus.h"
> > #include "hw/virtio/virtio-access.h"
> > +#include "hw/virtio/virtio-pci.h"
> > #include "sysemu/dma.h"
> >
> > /*
> > @@ -2681,6 +2682,44 @@ void virtio_device_release_ioeventfd(VirtIODevice *vdev)
> > virtio_bus_release_ioeventfd(vbus);
> > }
> >
> > +bool virtio_device_parent_is_pci_device(VirtIODevice *vdev)
> > +{
> > + BusState *qbus = qdev_get_parent_bus(DEVICE(vdev));
> > + const char *typename = object_get_typename(OBJECT(qbus->parent));
> > +
> > + return strstr(typename, "pci") != NULL;
> > +}
> > +
> > +bool virtio_device_page_per_vq_enabled(VirtIODevice *vdev)
> > +{
> > +#ifdef CONFIG_VIRTIO_PCI
> > + if (virtio_device_parent_is_pci_device(vdev)) {
> > + return virtio_pci_page_per_vq_enabled(vdev);
> > + }
> > +#endif
> > + return false;
> > +}
> > +
>
> A better way to do this is to pass a callback to the bus where each bus can
> implement its own.
>
It's pretty neat! It helped me get rid of all the
changes to the build scripts. Thanks a lot!
Best regards,
Tiwei Bie
next prev parent reply other threads:[~2018-03-27 13:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 7:15 [Qemu-devel] [PATCH v2 0/6] Extend vhost-user to support VFIO based accelerators Tiwei Bie
2018-03-19 7:15 ` [Qemu-devel] [PATCH v2 1/6] vhost-user: support receiving file descriptors in slave_read Tiwei Bie
2018-03-19 7:15 ` [Qemu-devel] [PATCH v2 2/6] vhost-user: introduce shared vhost-user state Tiwei Bie
2018-03-22 15:13 ` Michael S. Tsirkin
2018-03-27 13:32 ` [Qemu-devel] [virtio-dev] " Tiwei Bie
2018-03-19 7:15 ` [Qemu-devel] [PATCH v2 3/6] virtio: support adding sub-regions for notify region Tiwei Bie
2018-03-22 14:57 ` Michael S. Tsirkin
2018-03-27 13:47 ` Tiwei Bie [this message]
2018-03-19 7:15 ` [Qemu-devel] [PATCH v2 4/6] vfio: support getting VFIOGroup from groupfd Tiwei Bie
2018-03-19 7:15 ` [Qemu-devel] [PATCH v2 5/6] vfio: remove DPRINTF() definition from vfio-common.h Tiwei Bie
2018-03-22 15:15 ` Michael S. Tsirkin
2018-03-27 13:33 ` [Qemu-devel] [virtio-dev] " Tiwei Bie
2018-03-19 7:15 ` [Qemu-devel] [PATCH v2 6/6] vhost-user: add VFIO based accelerators support Tiwei Bie
2018-03-22 16:19 ` Michael S. Tsirkin
2018-03-27 11:06 ` Tiwei Bie
2018-03-27 13:59 ` Tiwei Bie
2018-03-22 14:55 ` [Qemu-devel] [PATCH v2 0/6] Extend vhost-user to support VFIO based accelerators Michael S. Tsirkin
2018-03-23 8:54 ` Tiwei Bie
2018-03-22 16:40 ` Michael S. Tsirkin
2018-03-28 12:24 ` Tiwei Bie
2018-03-28 15:33 ` Michael S. Tsirkin
2018-03-29 3:33 ` [Qemu-devel] [virtio-dev] " Tiwei Bie
2018-03-29 4:16 ` 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=20180327134705.3zqzangejm2yy3ph@debian \
--to=tiwei.bie@intel.com \
--cc=alex.williamson@redhat.com \
--cc=cunming.liang@intel.com \
--cc=dan.daly@intel.com \
--cc=jasowang@redhat.com \
--cc=jianfeng.tan@intel.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=xiao.w.wang@intel.com \
--cc=zhihong.wang@intel.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).