diff options
| author | Maciej S. Szmigiero <[email protected]> | 2022-05-02 00:07:25 +0200 |
|---|---|---|
| committer | Paolo Bonzini <[email protected]> | 2022-06-08 04:46:40 -0400 |
| commit | 00f08d99dd7d3ab3d8cb1fa356e857fcccbbdde8 (patch) | |
| tree | fff87eab93a741804e7769de93e2318ad49780e6 /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | 5552de7b928dc56de30eb74bcd7d439f49d0fe9d (diff) | |
KVM: nSVM: Sync next_rip field from vmcb12 to vmcb02
The next_rip field of a VMCB is *not* an output-only field for a VMRUN.
This field value (instead of the saved guest RIP) in used by the CPU for
the return address pushed on stack when injecting a software interrupt or
INT3 or INTO exception.
Make sure this field gets synced from vmcb12 to vmcb02 when entering L2 or
loading a nested state and NRIPS is exposed to L1. If NRIPS is supported
in hardware but not exposed to L1 (nrips=0 or hidden by userspace), stuff
vmcb02's next_rip from the new L2 RIP to emulate a !NRIPS CPU (which
saves RIP on the stack as-is).
Reviewed-by: Maxim Levitsky <[email protected]>
Co-developed-by: Sean Christopherson <[email protected]>
Signed-off-by: Sean Christopherson <[email protected]>
Signed-off-by: Maciej S. Szmigiero <[email protected]>
Message-Id: <c2e0a3d78db3ae30530f11d4e9254b452a89f42b.1651440202.git.maciej.szmigiero@oracle.com>
Signed-off-by: Paolo Bonzini <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions