diff options
author | 2020-10-26 16:54:07 +0530 | |
---|---|---|
committer | 2020-10-29 20:41:04 +0000 | |
commit | 91a2c34b7d6fadc9c5d9433c620ea4c32ee7cae8 (patch) | |
tree | af2a3c98477885147558233c175d6368ef24c77d /tools/perf/scripts/python/export-to-postgresql.py | |
parent | KVM: arm64: Use fallback mapping sizes for contiguous huge page sizes (diff) | |
download | wireguard-linux-91a2c34b7d6fadc9c5d9433c620ea4c32ee7cae8.tar.xz wireguard-linux-91a2c34b7d6fadc9c5d9433c620ea4c32ee7cae8.zip |
KVM: arm64: Force PTE mapping on fault resulting in a device mapping
VFIO allows a device driver to resolve a fault by mapping a MMIO
range. This can be subsequently result in user_mem_abort() to
try and compute a huge mapping based on the MMIO pfn, which is
a sure recipe for things to go wrong.
Instead, force a PTE mapping when the pfn faulted in has a device
mapping.
Fixes: 6d674e28f642 ("KVM: arm/arm64: Properly handle faulting of device mappings")
Suggested-by: Marc Zyngier <maz@kernel.org>
Signed-off-by: Santosh Shukla <sashukla@nvidia.com>
[maz: rewritten commit message]
Signed-off-by: Marc Zyngier <maz@kernel.org>
Reviewed-by: Gavin Shan <gshan@redhat.com>
Cc: stable@vger.kernel.org
Link: https://lore.kernel.org/r/1603711447-11998-2-git-send-email-sashukla@nvidia.com
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions