From: Bharat Bhushan <bbhushan2@marvell.com>
To: <peter.maydell@linaro.org>, <peterx@redhat.com>,
<eric.auger.pro@gmail.com>, <alex.williamson@redhat.com>,
<kevin.tian@intel.com>, <mst@redhat.com>, <tnowicki@marvell.com>,
<drjones@redhat.com>, <linuc.decode@gmail.com>,
<qemu-devel@nongnu.org>, <qemu-arm@nongnu.org>,
<bharatb.linux@gmail.com>, <jean-philippe@linaro.org>,
<yang.zhong@intel.com>
Cc: Bharat Bhushan <bbhushan2@marvell.com>
Subject: [PATCH v8 6/8] virtio-iommu: Call iommu notifier for attach/detach
Date: Wed, 18 Mar 2020 15:41:57 +0530 [thread overview]
Message-ID: <20200318101159.8767-7-bbhushan2@marvell.com> (raw)
In-Reply-To: <20200318101159.8767-1-bbhushan2@marvell.com>
iommu-notifier are called when a device is attached
or detached to as address-space.
This is needed for VFIO.
Signed-off-by: Bharat Bhushan <bbhushan2@marvell.com>
---
hw/virtio/virtio-iommu.c | 49 ++++++++++++++++++++++++++++++++++++++++
1 file changed, 49 insertions(+)
diff --git a/hw/virtio/virtio-iommu.c b/hw/virtio/virtio-iommu.c
index 623b477b9c..4d522a636a 100644
--- a/hw/virtio/virtio-iommu.c
+++ b/hw/virtio/virtio-iommu.c
@@ -49,6 +49,7 @@ typedef struct VirtIOIOMMUEndpoint {
uint32_t id;
VirtIOIOMMUDomain *domain;
QLIST_ENTRY(VirtIOIOMMUEndpoint) next;
+ VirtIOIOMMU *viommu;
} VirtIOIOMMUEndpoint;
typedef struct VirtIOIOMMUInterval {
@@ -155,11 +156,48 @@ static void virtio_iommu_notify_unmap(IOMMUMemoryRegion *mr, hwaddr iova,
memory_region_notify_iommu(mr, 0, entry);
}
+static gboolean virtio_iommu_mapping_unmap(gpointer key, gpointer value,
+ gpointer data)
+{
+ VirtIOIOMMUInterval *interval = (VirtIOIOMMUInterval *) key;
+ IOMMUMemoryRegion *mr = (IOMMUMemoryRegion *) data;
+
+ virtio_iommu_notify_unmap(mr, interval->low,
+ interval->high - interval->low + 1);
+
+ return false;
+}
+
+static gboolean virtio_iommu_mapping_map(gpointer key, gpointer value,
+ gpointer data)
+{
+ VirtIOIOMMUMapping *mapping = (VirtIOIOMMUMapping *) value;
+ VirtIOIOMMUInterval *interval = (VirtIOIOMMUInterval *) key;
+ IOMMUMemoryRegion *mr = (IOMMUMemoryRegion *) data;
+
+ virtio_iommu_notify_map(mr, interval->low, mapping->phys_addr,
+ interval->high - interval->low + 1);
+
+ return false;
+}
+
static void virtio_iommu_detach_endpoint_from_domain(VirtIOIOMMUEndpoint *ep)
{
+ VirtIOIOMMU *s = ep->viommu;
+ VirtIOIOMMUDomain *domain = ep->domain;
+ IOMMUDevice *sdev;
+
if (!ep->domain) {
return;
}
+
+ QLIST_FOREACH(sdev, &s->notifiers_list, next) {
+ if (ep->id == sdev->devfn) {
+ g_tree_foreach(domain->mappings, virtio_iommu_mapping_unmap,
+ &sdev->iommu_mr);
+ }
+ }
+
QLIST_REMOVE(ep, next);
ep->domain = NULL;
}
@@ -178,6 +216,7 @@ static VirtIOIOMMUEndpoint *virtio_iommu_get_endpoint(VirtIOIOMMU *s,
}
ep = g_malloc0(sizeof(*ep));
ep->id = ep_id;
+ ep->viommu = s;
trace_virtio_iommu_get_endpoint(ep_id);
g_tree_insert(s->endpoints, GUINT_TO_POINTER(ep_id), ep);
return ep;
@@ -274,6 +313,7 @@ static int virtio_iommu_attach(VirtIOIOMMU *s,
uint32_t ep_id = le32_to_cpu(req->endpoint);
VirtIOIOMMUDomain *domain;
VirtIOIOMMUEndpoint *ep;
+ IOMMUDevice *sdev;
trace_virtio_iommu_attach(domain_id, ep_id);
@@ -299,6 +339,14 @@ static int virtio_iommu_attach(VirtIOIOMMU *s,
ep->domain = domain;
+ /* Replay domain mappings on the associated memory region */
+ QLIST_FOREACH(sdev, &s->notifiers_list, next) {
+ if (ep_id == sdev->devfn) {
+ g_tree_foreach(domain->mappings, virtio_iommu_mapping_map,
+ &sdev->iommu_mr);
+ }
+ }
+
return VIRTIO_IOMMU_S_OK;
}
@@ -873,6 +921,7 @@ static gboolean reconstruct_endpoints(gpointer key, gpointer value,
QLIST_FOREACH(iter, &d->endpoint_list, next) {
iter->domain = d;
+ iter->viommu = s;
g_tree_insert(s->endpoints, GUINT_TO_POINTER(iter->id), iter);
}
return false; /* continue the domain traversal */
--
2.17.1
next prev parent reply other threads:[~2020-03-18 10:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 10:11 [PATCH v8 0/8] virtio-iommu: VFIO integration Bharat Bhushan
2020-03-18 10:11 ` [PATCH v8 1/8] hw/vfio/common: Remove error print on mmio region translation by viommu Bharat Bhushan
2020-03-18 10:11 ` [PATCH v8 2/8] memory: Add interface to set iommu page size mask Bharat Bhushan
2020-03-18 10:11 ` [PATCH v8 3/8] vfio: set iommu page size as per host supported page size Bharat Bhushan
2020-03-18 10:11 ` [PATCH v8 4/8] virtio-iommu: set supported page size mask Bharat Bhushan
2020-03-18 11:28 ` Auger Eric
2020-03-18 14:35 ` Bharat Bhushan
2020-03-23 8:43 ` Bharat Bhushan
2020-03-18 10:11 ` [PATCH v8 5/8] virtio-iommu: Add iommu notifier for map/unmap Bharat Bhushan
2020-03-18 10:11 ` Bharat Bhushan [this message]
2020-03-18 10:11 ` [PATCH v8 7/8] virtio-iommu: add iommu replay Bharat Bhushan
2020-03-18 10:11 ` [PATCH v8 8/8] virtio-iommu: add iommu notifier memory-region Bharat Bhushan
2020-03-18 10:53 ` [PATCH v8 0/8] virtio-iommu: VFIO integration Auger Eric
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=20200318101159.8767-7-bbhushan2@marvell.com \
--to=bbhushan2@marvell.com \
--cc=alex.williamson@redhat.com \
--cc=bharatb.linux@gmail.com \
--cc=drjones@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=jean-philippe@linaro.org \
--cc=kevin.tian@intel.com \
--cc=linuc.decode@gmail.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=tnowicki@marvell.com \
--cc=yang.zhong@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).