summaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm
diff options
context:
space:
mode:
authorSean Christopherson <seanjc@google.com>2023-07-28 18:35:20 -0700
committerPaolo Bonzini <pbonzini@redhat.com>2023-08-31 13:49:00 -0400
commit932844462ae310493d0d21b1c5d7464d59702b4d (patch)
tree6c9d225ec0c9aa2af4c0e26bc52a0af07f4b410d /drivers/gpu/drm
parenteeb87272a364311dbfe1b10dd896c3e09a02cd03 (diff)
downloadlinux-stable-932844462ae310493d0d21b1c5d7464d59702b4d.tar.gz
linux-stable-932844462ae310493d0d21b1c5d7464d59702b4d.tar.bz2
linux-stable-932844462ae310493d0d21b1c5d7464d59702b4d.zip
KVM: x86/mmu: Don't bounce through page-track mechanism for guest PTEs
Don't use the generic page-track mechanism to handle writes to guest PTEs in KVM's MMU. KVM's MMU needs access to information that should not be exposed to external page-track users, e.g. KVM needs (for some definitions of "need") the vCPU to query the current paging mode, whereas external users, i.e. KVMGT, have no ties to the current vCPU and so should never need the vCPU. Moving away from the page-track mechanism will allow dropping use of the page-track mechanism for KVM's own MMU, and will also allow simplifying and cleaning up the page-track APIs. Reviewed-by: Yan Zhao <yan.y.zhao@intel.com> Tested-by: Yongwei Ma <yongwei.ma@intel.com> Link: https://lore.kernel.org/r/20230729013535.1070024-15-seanjc@google.com Signed-off-by: Sean Christopherson <seanjc@google.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'drivers/gpu/drm')
0 files changed, 0 insertions, 0 deletions