From: Peter Xu <peterx@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
mst@redhat.com, jasowang@redhat.com, qemu-devel@nongnu.org,
cornelia.huck@de.ibm.com, alex.williamson@redhat.com,
wexu@redhat.com, vkaplans@redhat.com, dgibson@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/3] memory: add iommu_notify_flag
Date: Tue, 6 Sep 2016 13:55:08 +0800 [thread overview]
Message-ID: <20160906055508.GD21051@pxdev.xzpeter.org> (raw)
In-Reply-To: <20160906051846.GD16479@voom.fritz.box>
On Tue, Sep 06, 2016 at 03:18:46PM +1000, David Gibson wrote:
> > Maybe here naming the flags as IOMMU_{RW_NONE} is a little bit
> > confusing (just to leverage existing access flags), but what I was
> > trying to do is to make the two things not overlapped at all, since I
> > didn't find a mixture use case.
>
> Maybe not now, but a common use case is absolutely possible. If you
> had a single (guest) bus with a single IO address space, with vIOMMU
> and both VFIO and vhost devices on it, the same vIOMMU would need to
> send all notifications to VFIO and (at least) unmap notifications to
> vhost.
Yeah this is a good one... Thanks to point out.
Then I agree that splitting the use cases won't be enough... We may
need to exactly register IOMMU notifiers with notification type
(invalidations only, or we also need entry additions), and we just
selectively notify the consumers depending on what kind of
notification it is.
Or any smarter way to do it.
-- peterx
next prev parent reply other threads:[~2016-09-06 5:55 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 [this message]
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 ` [Qemu-devel] [PATCH 0/3] memory: add IOMMU notifier type David Gibson
2016-09-06 5:49 ` 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=20160906055508.GD21051@pxdev.xzpeter.org \
--to=peterx@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=cornelia.huck@de.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=dgibson@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@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.