aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c
diff options
context:
space:
mode:
authorOliver Upton <[email protected]>2022-12-07 21:48:07 +0000
committerPaolo Bonzini <[email protected]>2022-12-09 08:13:35 +0000
commite8b9a055fa0481679132781db574ecb771960f16 (patch)
treec27dabafacc1cd6966c6626e9ddabf4deb026442 /drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c
parentMerge tag 'kvmarm-6.2' of https://git.kernel.org/pub/scm/linux/kernel/git/kvm... (diff)
downloadkernel-e8b9a055fa0481679132781db574ecb771960f16.tar.gz
kernel-e8b9a055fa0481679132781db574ecb771960f16.zip
KVM: arm64: selftests: Align VA space allocator with TTBR0
An interesting feature of the Arm architecture is that the stage-1 MMU supports two distinct VA regions, controlled by TTBR{0,1}_EL1. As KVM selftests on arm64 only uses TTBR0_EL1, the VA space is constrained to [0, 2^(va_bits-1)). This is different from other architectures that allow for addressing low and high regions of the VA space from a single page table. KVM selftests' VA space allocator presumes the valid address range is split between low and high memory based the MSB, which of course is a poor match for arm64's TTBR0 region. Allow architectures to override the default VA space layout. Make use of the override to align vpages_valid with the behavior of TTBR0 on arm64. Signed-off-by: Oliver Upton <[email protected]> Message-Id: <[email protected]> Signed-off-by: Paolo Bonzini <[email protected]>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c')
0 files changed, 0 insertions, 0 deletions