summaryrefslogtreecommitdiff
path: root/scripts/gdb/linux/utils.py
diff options
context:
space:
mode:
authorSean Christopherson <seanjc@google.com>2024-08-31 03:15:30 +0300
committerSean Christopherson <seanjc@google.com>2024-09-10 06:16:30 +0300
commit620525739521376a65a690df899e1596d56791f8 (patch)
treea332d0d8358d12089cea267bc7a408e69ce049f2 /scripts/gdb/linux/utils.py
parentb299c273c06f005976cdc1b9e9299d492527607e (diff)
downloadlinux-620525739521376a65a690df899e1596d56791f8.tar.xz
KVM: x86: Remove manual pfn lookup when retrying #PF after failed emulation
Drop the manual pfn look when retrying an instruction that KVM failed to emulation in response to a #PF due to a write-protected gfn. Now that KVM sets EMULTYPE_ALLOW_RETRY_PF if and only if the page fault hit a write- protected gfn, i.e. if and only if there's a writable memslot, there's no need to redo the lookup to avoid retrying an instruction that failed on emulated MMIO (no slot, or a write to a read-only slot). I.e. KVM will never attempt to retry an instruction that failed on emulated MMIO, whereas that was not the case prior to the introduction of RET_PF_WRITE_PROTECTED. Reviewed-by: Yuan Yao <yuan.yao@intel.com> Link: https://lore.kernel.org/r/20240831001538.336683-16-seanjc@google.com Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'scripts/gdb/linux/utils.py')
0 files changed, 0 insertions, 0 deletions