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 v5 3/3] intel_iommu: allow UNMAP notifiers
Date: Wed, 21 Sep 2016 13:49:10 +1000 [thread overview]
Message-ID: <20160921034910.GX20488@umbus> (raw)
In-Reply-To: <20160920072808.GE5134@pxdev.xzpeter.org>
[-- Attachment #1: Type: text/plain, Size: 1560 bytes --]
On Tue, Sep 20, 2016 at 03:28:08PM +0800, Peter Xu wrote:
> On Tue, Sep 20, 2016 at 04:14:09PM +1000, David Gibson wrote:
> > On Wed, Sep 14, 2016 at 04:25:48PM +0800, Peter Xu wrote:
> > > Intel vIOMMU is still lacking of a complete IOMMU notifier mechanism.
> > > Before that is achieved, let's open a door for vhost DMAR support, which
> > > only requires cache invalidations (UNMAP operations).
> > >
> > > Meanwhile, converting hw_error() to error_report() and exit(1), to make
> > > the error messages clean and obvious (so no CPU registers will be
> > > dumped).
> >
> > Erm... AIUI currently the intel iommu driver doesn't do any
> > notifications. Surely it's only valid to allow this once you've
> > implemented unmap side notifications.
>
> Yes, I suppose vhost DMAR patches will be based upon this one. I can
> postpone this patch until Jason wants to pick it up, but it actually
> does not hurt if we just enable it now, anyway no one is using it.
Even so, I think it's misleading to implicitly advertise a capability
that's not yet implemented. Changing this warning should happen after
or at the same time as implementing the notifications in the vIOMMU
model.
> So... I see no bad to merge this along with the series, so that we can
> reduce one entry from Jason's TODO list. :)
>
> Thanks!
>
> -- peterx
>
--
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: 819 bytes --]
next prev parent reply other threads:[~2016-09-21 3:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 8:25 [Qemu-devel] [PATCH v5 0/3] Introduce IOMMUNotifier struct Peter Xu
2016-09-14 8:25 ` [Qemu-devel] [PATCH v5 1/3] memory: introduce IOMMUNotifier and its caps Peter Xu
2016-09-20 6:12 ` David Gibson
2016-09-20 7:16 ` Peter Xu
2016-09-21 3:48 ` David Gibson
2016-09-14 8:25 ` [Qemu-devel] [PATCH v5 2/3] memory: introduce IOMMUOps.notify_flag_changed Peter Xu
2016-09-20 6:13 ` David Gibson
2016-09-14 8:25 ` [Qemu-devel] [PATCH v5 3/3] intel_iommu: allow UNMAP notifiers Peter Xu
2016-09-20 6:14 ` David Gibson
2016-09-20 7:28 ` Peter Xu
2016-09-21 3:49 ` David Gibson [this message]
2016-09-21 4:57 ` Peter Xu
2016-09-19 12:47 ` [Qemu-devel] [PATCH v5 0/3] Introduce IOMMUNotifier struct Paolo Bonzini
2016-09-20 6:14 ` 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=20160921034910.GX20488@umbus \
--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.