summaryrefslogtreecommitdiff
path: root/tools/gpio
diff options
context:
space:
mode:
authorSean Christopherson <sean.j.christopherson@intel.com>2020-01-08 23:24:38 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2020-02-11 15:34:17 +0300
commit21b70d9bc16e2d8377b61eb7913c047318a5a9be (patch)
treefd7c68529fcae36341c14ed2faf67f3b3bcf85a4 /tools/gpio
parentdabf1a1096b2cb7c54eecbaee19367cae2aef0e3 (diff)
downloadlinux-21b70d9bc16e2d8377b61eb7913c047318a5a9be.tar.xz
KVM: Play nice with read-only memslots when querying host page size
[ Upstream commit 42cde48b2d39772dba47e680781a32a6c4b7dc33 ] Avoid the "writable" check in __gfn_to_hva_many(), which will always fail on read-only memslots due to gfn_to_hva() assuming writes. Functionally, this allows x86 to create large mappings for read-only memslots that are backed by HugeTLB mappings. Note, the changelog for commit 05da45583de9 ("KVM: MMU: large page support") states "If the largepage contains write-protected pages, a large pte is not used.", but "write-protected" refers to pages that are temporarily read-only, e.g. read-only memslots didn't even exist at the time. Fixes: 4d8b81abc47b ("KVM: introduce readonly memslot") Cc: stable@vger.kernel.org Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com> [Redone using kvm_vcpu_gfn_to_memslot_prot. - Paolo] Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'tools/gpio')
0 files changed, 0 insertions, 0 deletions