diff options
author | Sean Christopherson <seanjc@google.com> | 2024-11-01 22:14:46 +0300 |
---|---|---|
committer | Sean Christopherson <seanjc@google.com> | 2024-12-19 18:34:13 +0300 |
commit | c829d2c35650e9e24dc338234bd14e4c7c6231f5 (patch) | |
tree | bba8d0814c37fb1f0d8e0a44752b978624227839 /tools/perf/scripts/python/parallel-perf.py | |
parent | b2868b55cfef036b743a620de18cb3ff1d16b043 (diff) | |
download | linux-c829d2c35650e9e24dc338234bd14e4c7c6231f5.tar.xz |
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 'tools/perf/scripts/python/parallel-perf.py')
0 files changed, 0 insertions, 0 deletions