aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/scripts/gdb/linux/utils.py
diff options
context:
space:
mode:
authorSean Christopherson <seanjc@google.com>2024-11-01 12:14:46 -0700
committerSean Christopherson <seanjc@google.com>2024-12-19 07:34:13 -0800
commitc829d2c35650e9e24dc338234bd14e4c7c6231f5 (patch)
treebba8d0814c37fb1f0d8e0a44752b978624227839 /scripts/gdb/linux/utils.py
parentKVM: nVMX: Drop manual vmcs01.GUEST_INTERRUPT_STATUS.RVI check at VM-Enter (diff)
downloadwireguard-linux-c829d2c35650e9e24dc338234bd14e4c7c6231f5.tar.xz
wireguard-linux-c829d2c35650e9e24dc338234bd14e4c7c6231f5.zip
KVM: nVMX: Use vmcs01's controls shadow to check for IRQ/NMI windows at VM-Enter
Use vmcs01's execution controls shadow to check for IRQ/NMI windows after a successful nested VM-Enter, instead of snapshotting the information prior to emulating VM-Enter. It's quite difficult to see that the entire reason controls are snapshot prior nested VM-Enter is to read them from vmcs01 (vmcs02 is loaded if nested VM-Enter is successful). That could be solved with a comment, but explicitly using vmcs01's shadow makes the code self-documenting to a certain extent. No functional change intended (vmcs01's execution controls must not be modified during emulation of nested VM-Enter). Link: https://lore.kernel.org/r/20241101191447.1807602-5-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