diff options
author | Yang Zhang <yang.z.zhang@Intel.com> | 2013-10-24 09:56:39 +0800 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2013-10-28 13:15:01 +0100 |
commit | e0230e1327fb862c9b6cde24ae62d55f9db62c9b (patch) | |
tree | 9579c57cd5b9f886fe6a8d1400d87560ec28d646 /arch/arm/kvm | |
parent | a294c9bbd0dd0dea415a0ee5b8ee9c07f65f5496 (diff) | |
download | op-kernel-dev-e0230e1327fb862c9b6cde24ae62d55f9db62c9b.zip op-kernel-dev-e0230e1327fb862c9b6cde24ae62d55f9db62c9b.tar.gz |
KVM: Mapping IOMMU pages after updating memslot
In kvm_iommu_map_pages(), we need to know the page size via call
kvm_host_page_size(). And it will check whether the target slot
is valid before return the right page size.
Currently, we will map the iommu pages when creating a new slot.
But we call kvm_iommu_map_pages() during preparing the new slot.
At that time, the new slot is not visible by domain(still in preparing).
So we cannot get the right page size from kvm_host_page_size() and
this will break the IOMMU super page logic.
The solution is to map the iommu pages after we insert the new slot
into domain.
Signed-off-by: Yang Zhang <yang.z.zhang@Intel.com>
Tested-by: Patrick Lu <patrick.lu@intel.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'arch/arm/kvm')
0 files changed, 0 insertions, 0 deletions