[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v4 1/3] memory: introduce IOMMUNotifier and its
From: |
Peter Xu |
Subject: |
Re: [Qemu-devel] [PATCH v4 1/3] memory: introduce IOMMUNotifier and its caps |
Date: |
Wed, 14 Sep 2016 16:17:26 +0800 |
User-agent: |
Mutt/1.5.24 (2015-08-30) |
On Wed, Sep 14, 2016 at 05:15:03PM +1000, David Gibson wrote:
[...]
> Peter suggested commenting this next to the IOTLBEntry definition, and
> I think that's probably ok for now.
Looks like we have something already (just not that obvious):
/**
* memory_region_notify_iommu: notify a change in an IOMMU translation entry.
*
* @mr: the memory region that was changed
* @entry: the new entry in the IOMMU translation table. The entry
* replaces all old entries for the same virtual I/O address range.
* Deleted entries have address@hidden == 0.
*/
void memory_region_notify_iommu(MemoryRegion *mr,
IOMMUTLBEntry entry);
Though it's quite simple, it did explain that perm==0 is for deleted
entries.
Thanks,
-- peterx
[Qemu-devel] [PATCH v4 2/3] memory: introduce IOMMUOps.notify_flag_changed, Peter Xu, 2016/09/08
- Re: [Qemu-devel] [PATCH v4 2/3] memory: introduce IOMMUOps.notify_flag_changed, David Gibson, 2016/09/14
- Re: [Qemu-devel] [PATCH v4 2/3] memory: introduce IOMMUOps.notify_flag_changed, Peter Xu, 2016/09/14
- Re: [Qemu-devel] [PATCH v4 2/3] memory: introduce IOMMUOps.notify_flag_changed, David Gibson, 2016/09/14
- Re: [Qemu-devel] [PATCH v4 2/3] memory: introduce IOMMUOps.notify_flag_changed, Peter Xu, 2016/09/14
- Re: [Qemu-devel] [PATCH v4 2/3] memory: introduce IOMMUOps.notify_flag_changed, David Gibson, 2016/09/14
- Re: [Qemu-devel] [PATCH v4 2/3] memory: introduce IOMMUOps.notify_flag_changed, Peter Xu, 2016/09/14
[Qemu-devel] [PATCH v4 3/3] intel_iommu: allow UNMAP notifiers, Peter Xu, 2016/09/08