[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v4 2/3] memory: introduce IOMMUOps.notify_flag_c
From: |
Peter Xu |
Subject: |
Re: [Qemu-devel] [PATCH v4 2/3] memory: introduce IOMMUOps.notify_flag_changed |
Date: |
Wed, 14 Sep 2016 19:25:32 +0800 |
User-agent: |
Mutt/1.5.24 (2015-08-30) |
On Wed, Sep 14, 2016 at 08:37:34PM +1000, David Gibson wrote:
[...]
> > This should not be related to the interface at all?
> >
> > I was based on the assumption that "Power cannot support either one of
> > MAP/UNMAP, but only if both exist".
>
> Huh? I have no idea what you mean by that.
>
> Power can support notifying both map and unmap events just fine - but
> in order to provide *any* notifications, it has to disable KVM
> acceleration of the guest-side IOMMU (otherwise qemu won't know about
> any changes to the IOMMU state).
>
> So the change you you suggested before to != IOMMU_NOTIFIER_NONE is
> exactly correct, anything else is not.
Sorry I was wrong. Yes user can register with only one (MAP or UNMAP)
notifier type for any platform.
Thanks.
-- peterx
[Qemu-devel] [PATCH v4 2/3] memory: introduce IOMMUOps.notify_flag_changed, Peter Xu, 2016/09/08
[Qemu-devel] [PATCH v4 3/3] intel_iommu: allow UNMAP notifiers, Peter Xu, 2016/09/08
Re: [Qemu-devel] [PATCH v4 0/3] Introduce IOMMUNotifier struct, no-reply, 2016/09/09