diff options
author | Yan Zhao <yan.y.zhao@intel.com> | 2019-06-25 11:21:18 +0800 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2019-08-20 17:26:18 +0200 |
commit | 03c7140c1a0336af3d4fca768de791b9c0e2b128 (patch) | |
tree | 00d655bf4eb397f056fdff0569b95dbef572717c /tcg/tcg.h | |
parent | e502fe96ac4343a3f4a3c13f28eea03ae7b11c3f (diff) | |
download | qemu-03c7140c1a0336af3d4fca768de791b9c0e2b128.zip qemu-03c7140c1a0336af3d4fca768de791b9c0e2b128.tar.gz qemu-03c7140c1a0336af3d4fca768de791b9c0e2b128.tar.bz2 |
memory: assert on out of scope notification
It is wrong for an entry to have parts out of scope of notifier's range.
assert this condition.
Out of scope mapping/unmapping would cause problem, as in below case:
1. initially there are two notifiers with ranges
0-0xfedfffff, 0xfef00000-0xffffffffffffffff,
IOVAs from 0x3c000000 - 0x3c1fffff is in shadow page table.
2. in vfio, memory_region_register_iommu_notifier() is followed by
memory_region_iommu_replay(), which will first call address space
unmap,
and walk and add back all entries in vtd shadow page table. e.g.
(1) for notifier 0-0xfedfffff,
IOVAs from 0 - 0xffffffff get unmapped,
and IOVAs from 0x3c000000 - 0x3c1fffff get mapped
(2) for notifier 0xfef00000-0xffffffffffffffff
IOVAs from 0 - 0x7fffffffff get unmapped,
but IOVAs from 0x3c000000 - 0x3c1fffff cannot get mapped back.
Cc: Eric Auger <eric.auger@redhat.com>
Signed-off-by: Yan Zhao <yan.y.zhao@intel.com>
Message-Id: <1561432878-13754-1-git-send-email-yan.y.zhao@intel.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tcg/tcg.h')
0 files changed, 0 insertions, 0 deletions