From: Alex Williamson <alex.williamson@redhat.com>
To: mst@redhat.com, pbonzini@redhat.com
Cc: qemu-devel@nongnu.org, aik@ozlabs.ru, bd.aviv@gmail.com,
peterx@redhat.com, marcel@redhat.com,
david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [PATCH 0/2] memory/intel_iommu: Generate error for incompatible usage
Date: Tue, 28 Jun 2016 08:49:24 -0600 [thread overview]
Message-ID: <20160628084924.43566423@t450s.home> (raw)
In-Reply-To: <20160615154203.32658.82724.stgit@gimli.home>
Paolo & Michael,
Any comments on this series? I think we need Paolo's ack for the memory
changes and either of your ack for hw/i386/. I'm happy to pull this
through my tree with your approval though. Thanks,
Alex
On Wed, 15 Jun 2016 09:56:03 -0600
Alex Williamson <alex.williamson@redhat.com> wrote:
> VT-d emulation is currently incompatible with device assignment due
> to intel_iommu's lack of support for memory_region_notify_iommu().
> Alexey has proposed a nice addition to the MemoryRegionIOMMUOps
> structure that adds callbacks when the first iommu notifier is
> registered and the last is removed. For POWER this will allow them
> to switch the view of the iommu depending on whether anyone in
> userspace is watching. For VT-d I expect that eventually we'll use
> these callbacks to enable and disable code paths so that we avoid
> notifier overhead when there are no registered notifiy-ees. For now,
> we don't support calling memory_region_notify_iommu(), so this
> signals an incompatible hardware configuration. If we choose to make
> CM=0 a user selectable option, something like this might continue to
> be useful if we only support notifies via invalidations rather than
> full VT-d data structure shadowing.
>
> Even though we're currently working on enabling users like vfio-pci
> with VT-d, I believe this is correct for the current state of things.
> We might even want to consider this stable for v2.6.x so that
> downstreams pick it up to avoid incompatible configurations.
>
> Alexey, I hope I'm not stepping on your toes by extracting this
> from your latest patch series. Please let us know whether you
> approve. Thanks,
>
> Alex
>
> ---
>
> Alex Williamson (1):
> intel_iommu: Throw hw_error on notify_started
>
> Alexey Kardashevskiy (1):
> memory: Add MemoryRegionIOMMUOps.notify_started/stopped callbacks
>
>
> hw/i386/intel_iommu.c | 12 ++++++++++++
> hw/vfio/common.c | 5 +++--
> include/exec/memory.h | 8 +++++++-
> memory.c | 10 +++++++++-
> 4 files changed, 31 insertions(+), 4 deletions(-)
next prev parent reply other threads:[~2016-06-28 14:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 15:56 [Qemu-devel] [PATCH 0/2] memory/intel_iommu: Generate error for incompatible usage Alex Williamson
2016-06-15 15:56 ` [Qemu-devel] [PATCH 1/2] memory: Add MemoryRegionIOMMUOps.notify_started/stopped callbacks Alex Williamson
2016-06-15 15:56 ` [Qemu-devel] [PATCH 2/2] intel_iommu: Throw hw_error on notify_started Alex Williamson
2016-06-16 1:12 ` David Gibson
2016-06-16 7:22 ` Marcel Apfelbaum
2016-06-16 1:43 ` [Qemu-devel] [PATCH 0/2] memory/intel_iommu: Generate error for incompatible usage Alexey Kardashevskiy
2016-06-27 4:46 ` Alexey Kardashevskiy
2016-06-27 5:12 ` Alex Williamson
2016-06-16 3:21 ` Peter Xu
2016-06-28 14:49 ` Alex Williamson [this message]
2016-06-29 10:53 ` Paolo Bonzini
2016-06-29 15:56 ` Alex Williamson
2016-06-29 15:58 ` Paolo Bonzini
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=20160628084924.43566423@t450s.home \
--to=alex.williamson@redhat.com \
--cc=aik@ozlabs.ru \
--cc=bd.aviv@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).