From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: tianyu.lan@intel.com, kevin.tian@intel.com, mst@redhat.com,
jan.kiszka@siemens.com, jasowang@redhat.com, peterx@redhat.com,
alex.williamson@redhat.com, bd.aviv@gmail.com
Subject: [Qemu-devel] [PATCH RFC v2 13/17] memory: add MemoryRegionIOMMUOps.replay() callback
Date: Tue, 3 Jan 2017 15:29:50 +0800 [thread overview]
Message-ID: <1483428594-28880-14-git-send-email-peterx@redhat.com> (raw)
In-Reply-To: <1483428594-28880-1-git-send-email-peterx@redhat.com>
Originally we have one memory_region_iommu_replay() function, which is
the default behavior to replay the translations of the whole IOMMU
region. However, on some platform like x86, we may want our own replay
logic for IOMMU regions. This patch add one more hook for IOMMUOps for
the callback, and it'll override the default if set.
Signed-off-by: Peter Xu <peterx@redhat.com>
---
include/exec/memory.h | 2 ++
memory.c | 6 ++++++
2 files changed, 8 insertions(+)
diff --git a/include/exec/memory.h b/include/exec/memory.h
index afe150c..a26763f 100644
--- a/include/exec/memory.h
+++ b/include/exec/memory.h
@@ -181,6 +181,8 @@ struct MemoryRegionIOMMUOps {
void (*notify_flag_changed)(MemoryRegion *iommu,
IOMMUNotifierFlag old_flags,
IOMMUNotifierFlag new_flags);
+ /* Set this up to provide customized IOMMU replay function */
+ void (*replay)(MemoryRegion *iommu, IOMMUNotifier *notifier);
};
typedef struct CoalescedMemoryRange CoalescedMemoryRange;
diff --git a/memory.c b/memory.c
index 6e4c872..609ac67 100644
--- a/memory.c
+++ b/memory.c
@@ -1629,6 +1629,12 @@ void memory_region_iommu_replay(MemoryRegion *mr, IOMMUNotifier *n,
hwaddr addr, granularity;
IOMMUTLBEntry iotlb;
+ /* If the IOMMU has its own replay callback, override */
+ if (mr->iommu_ops->replay) {
+ mr->iommu_ops->replay(mr, n);
+ return;
+ }
+
granularity = memory_region_iommu_get_min_page_size(mr);
for (addr = 0; addr < memory_region_size(mr); addr += granularity) {
--
2.7.4
next prev parent reply other threads:[~2017-01-03 7:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 7:29 [Qemu-devel] [PATCH RFC v2 00/17] VT-d: vfio enablement and misc enhances Peter Xu
2017-01-03 7:29 ` [Qemu-devel] [PATCH RFC v2 01/17] IOMMU: add option to enable VTD_CAP_CM to vIOMMU capility exposoed to guest Peter Xu
2017-01-03 7:29 ` [Qemu-devel] [PATCH RFC v2 02/17] memory: handle alias for iommu notifier Peter Xu
2017-01-03 7:29 ` [Qemu-devel] [PATCH RFC v2 03/17] memory: handle alias in memory_region_is_iommu() Peter Xu
2017-01-03 7:29 ` [Qemu-devel] [PATCH RFC v2 04/17] intel_iommu: allocate new key when creating new address space Peter Xu
2017-01-03 7:29 ` [Qemu-devel] [PATCH RFC v2 05/17] intel_iommu: simplify irq region translation Peter Xu
2017-01-03 7:29 ` [Qemu-devel] [PATCH RFC v2 06/17] intel_iommu: renaming gpa to iova where proper Peter Xu
2017-01-03 7:29 ` [Qemu-devel] [PATCH RFC v2 07/17] intel_iommu: fix trace for inv desc handling Peter Xu
2017-01-03 7:29 ` [Qemu-devel] [PATCH RFC v2 08/17] intel_iommu: fix trace for addr translation Peter Xu
2017-01-03 7:29 ` [Qemu-devel] [PATCH RFC v2 09/17] intel_iommu: vtd_slpt_level_shift check level Peter Xu
2017-01-03 7:29 ` [Qemu-devel] [PATCH RFC v2 10/17] memory: add section range info for IOMMU notifier Peter Xu
2017-01-03 7:29 ` [Qemu-devel] [PATCH RFC v2 11/17] memory: provide iommu_replay_all() Peter Xu
2017-01-03 7:29 ` [Qemu-devel] [PATCH RFC v2 12/17] memory: introduce memory_region_notify_one() Peter Xu
2017-01-03 7:29 ` Peter Xu [this message]
2017-01-03 7:29 ` [Qemu-devel] [PATCH RFC v2 14/17] intel_iommu: provide its own replay() callback Peter Xu
2017-01-03 7:29 ` [Qemu-devel] [PATCH RFC v2 15/17] intel_iommu: do replay when context invalidate Peter Xu
2017-01-03 7:29 ` [Qemu-devel] [PATCH RFC v2 16/17] intel_iommu: allow dynamic switch of IOMMU region Peter Xu
2017-01-03 7:29 ` [Qemu-devel] [PATCH RFC v2 17/17] intel_iommu: enable vfio devices Peter Xu
2017-01-03 7:52 ` [Qemu-devel] [PATCH RFC v2 00/17] VT-d: vfio enablement and misc enhances no-reply
2017-01-12 14:27 ` Michael S. Tsirkin
2017-01-13 2:19 ` Peter Xu
2017-01-13 2:57 ` Peter Xu
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=1483428594-28880-14-git-send-email-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=bd.aviv@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=jasowang@redhat.com \
--cc=kevin.tian@intel.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tianyu.lan@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).