summaryrefslogtreecommitdiffstats
path: root/init
diff options
context:
space:
mode:
authorPaul Durrant <pdurrant@amazon.com>2024-02-15 15:29:00 +0000
committerSean Christopherson <seanjc@google.com>2024-02-20 07:37:43 -0800
commita4bff3df51472f555ab8dea05a3d2faf4abbf199 (patch)
tree7e692f20f629b2bd95844e42f86d2e38beb7016a /init
parent78b74638eb6dffd9b24bc3b121556a9039292df6 (diff)
downloadlinux-stable-a4bff3df51472f555ab8dea05a3d2faf4abbf199.tar.gz
linux-stable-a4bff3df51472f555ab8dea05a3d2faf4abbf199.tar.bz2
linux-stable-a4bff3df51472f555ab8dea05a3d2faf4abbf199.zip
KVM: pfncache: remove KVM_GUEST_USES_PFN usage
As noted in [1] the KVM_GUEST_USES_PFN usage flag is never set by any callers of kvm_gpc_init(), and for good reason: the implementation is incomplete/broken. And it's not clear that there will ever be a user of KVM_GUEST_USES_PFN, as coordinating vCPUs with mmu_notifier events is non-trivial. Remove KVM_GUEST_USES_PFN and all related code, e.g. dropping KVM_GUEST_USES_PFN also makes the 'vcpu' argument redundant, to avoid having to reason about broken code as __kvm_gpc_refresh() evolves. Moreover, all existing callers specify KVM_HOST_USES_PFN so the usage check in hva_to_pfn_retry() and hence the 'usage' argument to kvm_gpc_init() are also redundant. [1] https://lore.kernel.org/all/ZQiR8IpqOZrOpzHC@google.com Signed-off-by: Paul Durrant <pdurrant@amazon.com> Reviewed-by: David Woodhouse <dwmw@amazon.co.uk> Link: https://lore.kernel.org/r/20240215152916.1158-6-paul@xen.org [sean: explicitly call out that guest usage is incomplete] Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions