qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Viktor Prutyanov <viktor@daynix.com>
To: mst@redhat.com, Jason Wang <jasowang@redhat.com>
Cc: qemu-devel@nongnu.org, yan@daynix.com,
	yuri.benditovich@daynix.com,  qemu-stable@nongnu.org
Subject: Re: [PATCH v3 1/3] virtio-pci: add handling of PCI ATS and Device-TLB enable/disable
Date: Tue, 18 Jul 2023 14:14:26 +0300	[thread overview]
Message-ID: <CAPv0NP5MYkhFyfO3WwJA-EGWbMgCqBA-6AqP0juFE+mF+0zRkA@mail.gmail.com> (raw)
In-Reply-To: <CACGkMEtnTHipbuWu6BCgm=wMpekO7Ov2H4OnN47jhrnjQpCjsg@mail.gmail.com>

Add qemu-stable@nongnu.org

On Thu, May 18, 2023 at 9:10 AM Jason Wang <jasowang@redhat.com> wrote:
>
> On Fri, May 12, 2023 at 9:51 PM Viktor Prutyanov <viktor@daynix.com> wrote:
> >
> > According to PCIe Address Translation Services specification 5.1.3.,
> > ATS Control Register has Enable bit to enable/disable ATS. Guest may
> > enable/disable PCI ATS and, accordingly, Device-TLB for the VirtIO PCI
> > device. So, raise/lower a flag and call a trigger function to pass this
> > event to a device implementation.
> >
> > Signed-off-by: Viktor Prutyanov <viktor@daynix.com>
>
> Acked-by: Jason Wang <jasowang@redhat.com>
>
> Thanks
>
> > ---
> >  hw/virtio/virtio-pci.c     | 36 ++++++++++++++++++++++++++++++++++++
> >  include/hw/virtio/virtio.h |  2 ++
> >  2 files changed, 38 insertions(+)
> >
> > diff --git a/hw/virtio/virtio-pci.c b/hw/virtio/virtio-pci.c
> > index 02fb84a8fa..edbc0daa18 100644
> > --- a/hw/virtio/virtio-pci.c
> > +++ b/hw/virtio/virtio-pci.c
> > @@ -716,6 +716,38 @@ virtio_address_space_read(VirtIOPCIProxy *proxy, hwaddr addr,
> >      }
> >  }
> >
> > +static void virtio_pci_ats_ctrl_trigger(PCIDevice *pci_dev, bool enable)
> > +{
> > +    VirtIOPCIProxy *proxy = VIRTIO_PCI(pci_dev);
> > +    VirtIODevice *vdev = virtio_bus_get_device(&proxy->bus);
> > +    VirtioDeviceClass *k = VIRTIO_DEVICE_GET_CLASS(vdev);
> > +
> > +    vdev->device_iotlb_enabled = enable;
> > +
> > +    if (k->toggle_device_iotlb) {
> > +        k->toggle_device_iotlb(vdev);
> > +    }
> > +}
> > +
> > +static void pcie_ats_config_write(PCIDevice *dev, uint32_t address,
> > +                                  uint32_t val, int len)
> > +{
> > +    uint32_t off;
> > +    uint16_t ats_cap = dev->exp.ats_cap;
> > +
> > +    if (!ats_cap || address < ats_cap) {
> > +        return;
> > +    }
> > +    off = address - ats_cap;
> > +    if (off >= PCI_EXT_CAP_ATS_SIZEOF) {
> > +        return;
> > +    }
> > +
> > +    if (range_covers_byte(off, len, PCI_ATS_CTRL + 1)) {
> > +        virtio_pci_ats_ctrl_trigger(dev, !!(val & PCI_ATS_CTRL_ENABLE));
> > +    }
> > +}
> > +
> >  static void virtio_write_config(PCIDevice *pci_dev, uint32_t address,
> >                                  uint32_t val, int len)
> >  {
> > @@ -729,6 +761,10 @@ static void virtio_write_config(PCIDevice *pci_dev, uint32_t address,
> >          pcie_cap_flr_write_config(pci_dev, address, val, len);
> >      }
> >
> > +    if (proxy->flags & VIRTIO_PCI_FLAG_ATS) {
> > +        pcie_ats_config_write(pci_dev, address, val, len);
> > +    }
> > +
> >      if (range_covers_byte(address, len, PCI_COMMAND)) {
> >          if (!(pci_dev->config[PCI_COMMAND] & PCI_COMMAND_MASTER)) {
> >              virtio_set_disabled(vdev, true);
> > diff --git a/include/hw/virtio/virtio.h b/include/hw/virtio/virtio.h
> > index f6b38f7e9c..af86ed7249 100644
> > --- a/include/hw/virtio/virtio.h
> > +++ b/include/hw/virtio/virtio.h
> > @@ -155,6 +155,7 @@ struct VirtIODevice
> >      QLIST_HEAD(, VirtQueue) *vector_queues;
> >      QTAILQ_ENTRY(VirtIODevice) next;
> >      EventNotifier config_notifier;
> > +    bool device_iotlb_enabled;
> >  };
> >
> >  struct VirtioDeviceClass {
> > @@ -212,6 +213,7 @@ struct VirtioDeviceClass {
> >      const VMStateDescription *vmsd;
> >      bool (*primary_unplug_pending)(void *opaque);
> >      struct vhost_dev *(*get_vhost)(VirtIODevice *vdev);
> > +    void (*toggle_device_iotlb)(VirtIODevice *vdev);
> >  };
> >
> >  void virtio_instance_init_common(Object *proxy_obj, void *data,
> > --
> > 2.35.1
> >
>


  reply	other threads:[~2023-07-18 11:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12 13:51 [PATCH v3 0/3] vhost: register and change IOMMU flag depending on ATS state Viktor Prutyanov
2023-05-12 13:51 ` [PATCH v3 1/3] virtio-pci: add handling of PCI ATS and Device-TLB enable/disable Viktor Prutyanov
2023-05-18  6:10   ` Jason Wang
2023-07-18 11:14     ` Viktor Prutyanov [this message]
2023-05-12 13:51 ` [PATCH v3 2/3] vhost: register and change IOMMU flag depending on Device-TLB state Viktor Prutyanov
2023-05-18  6:14   ` Jason Wang
2023-05-19 17:49     ` Viktor Prutyanov
2023-05-24  8:25       ` Jason Wang
2023-05-25 12:55         ` Viktor Prutyanov
2023-05-26  1:33           ` Jason Wang
2023-05-12 13:51 ` [PATCH v3 3/3] virtio-net: pass Device-TLB enable/disable events to vhost Viktor Prutyanov

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=CAPv0NP5MYkhFyfO3WwJA-EGWbMgCqBA-6AqP0juFE+mF+0zRkA@mail.gmail.com \
    --to=viktor@daynix.com \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=yan@daynix.com \
    --cc=yuri.benditovich@daynix.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).