aboutsummaryrefslogtreecommitdiff
path: root/scripts/gdb/linux/timerlist.py
diff options
context:
space:
mode:
authorSean Christopherson <[email protected]>2022-04-23 03:47:46 +0000
committerPaolo Bonzini <[email protected]>2022-05-12 09:51:42 -0400
commit5276c616abf149a4dfbc708df3f22da642ec3dde (patch)
treeffe66fc3428e53f45f6158cafcad7134b08a059a /scripts/gdb/linux/timerlist.py
parent5c64aba5179f6fc6a367f76342c6290a5e06cfc4 (diff)
KVM: x86/mmu: Add RET_PF_CONTINUE to eliminate bool+int* "returns"
Add RET_PF_CONTINUE and use it in handle_abnormal_pfn() and kvm_faultin_pfn() to signal that the page fault handler should continue doing its thing. Aside from being gross and inefficient, using a boolean return to signal continue vs. stop makes it extremely difficult to add more helpers and/or move existing code to a helper. E.g. hypothetically, if nested MMUs were to gain a separate page fault handler in the future, everything up to the "is self-modifying PTE" check can be shared by all shadow MMUs, but communicating up the stack whether to continue on or stop becomes a nightmare. More concretely, proposed support for private guest memory ran into a similar issue, where it'll be forced to forego a helper in order to yield sane code: https://lore.kernel.org/all/YkJbxiL%[email protected]. No functional change intended. Cc: David Matlack <[email protected]> Cc: Chao Peng <[email protected]> Signed-off-by: Sean Christopherson <[email protected]> Message-Id: <[email protected]> Signed-off-by: Paolo Bonzini <[email protected]>
Diffstat (limited to 'scripts/gdb/linux/timerlist.py')
0 files changed, 0 insertions, 0 deletions