From: David Gibson <david@gibson.dropbear.id.au>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, mst@redhat.com, jasowang@redhat.com,
vkaplans@redhat.com, alex.williamson@redhat.com, wexu@redhat.com,
pbonzini@redhat.com, cornelia.huck@de.ibm.com,
dgibson@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/3] memory: add IOMMU notifier type
Date: Tue, 6 Sep 2016 15:06:17 +1000 [thread overview]
Message-ID: <20160906050617.GB16479@voom.fritz.box> (raw)
In-Reply-To: <1473060081-17835-1-git-send-email-peterx@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]
On Mon, Sep 05, 2016 at 03:21:18PM +0800, Peter Xu wrote:
> In the thread:
>
> https://lists.gnu.org/archive/html/qemu-devel/2016-09/msg00254.html
>
> Alex proposed a way for vhost DMAR to be enabled without breaking
> existing protections on vIOMMU and device assignments. This series
> tried to implement the idea, by introducing a IOMMU notifier type for
> each IOMMU memory region.
Hrm, I'm pretty dubious about this concept, since it's basically just
an interim hack for an incomplete notifier implementation on x86.
What makes just fixing the notifier so difficult?
>
> Thanks,
>
> Peter Xu (3):
> memory: add one flag for IOMMU notifier
> memory: add iommu_notify_flag
> intel_iommu: allow IOMMU_NONE typed notifiers
>
> hw/i386/intel_iommu.c | 13 ++++++++-----
> hw/ppc/spapr_iommu.c | 5 +++--
> hw/s390x/s390-pci-inst.c | 2 +-
> hw/vfio/common.c | 3 ++-
> include/exec/memory.h | 14 +++++++++++---
> memory.c | 12 +++++++++---
> 6 files changed, 34 insertions(+), 15 deletions(-)
>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2016-09-06 5:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 7:21 [Qemu-devel] [PATCH 0/3] memory: add IOMMU notifier type Peter Xu
2016-09-05 7:21 ` [Qemu-devel] [PATCH 1/3] memory: add one flag for IOMMU notifier Peter Xu
2016-09-05 7:21 ` [Qemu-devel] [PATCH 2/3] memory: add iommu_notify_flag Peter Xu
2016-09-05 8:04 ` Paolo Bonzini
2016-09-05 8:38 ` Peter Xu
2016-09-05 9:56 ` Paolo Bonzini
2016-09-06 5:27 ` Peter Xu
2016-09-06 7:51 ` Paolo Bonzini
2016-09-06 8:17 ` Peter Xu
2016-09-06 8:19 ` Paolo Bonzini
2016-09-06 10:31 ` Peter Xu
2016-09-07 5:44 ` David Gibson
2016-09-07 6:34 ` Peter Xu
2016-09-07 6:41 ` David Gibson
2016-09-08 9:07 ` Peter Xu
2016-09-12 1:26 ` David Gibson
2016-09-12 5:13 ` Peter Xu
2016-09-14 4:00 ` David Gibson
2016-09-14 5:43 ` Peter Xu
2016-09-06 5:18 ` David Gibson
2016-09-06 5:55 ` Peter Xu
2016-09-06 5:12 ` David Gibson
2016-09-06 5:33 ` Peter Xu
2016-09-05 7:21 ` [Qemu-devel] [PATCH 3/3] intel_iommu: allow IOMMU_NONE typed notifiers Peter Xu
2016-09-06 5:06 ` David Gibson [this message]
2016-09-06 5:49 ` [Qemu-devel] [PATCH 0/3] memory: add IOMMU notifier type Peter Xu
2016-09-06 6:26 ` Jason Wang
2016-09-07 4:38 ` David Gibson
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=20160906050617.GB16479@voom.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=alex.williamson@redhat.com \
--cc=cornelia.huck@de.ibm.com \
--cc=dgibson@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vkaplans@redhat.com \
--cc=wexu@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.