KVM: x86: Correct use of kvm_rip_read()
Status from this message: Queued, thanks.
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | KVM: x86: Do not use kvm_rip_read() unconditionally in KVM tracepointsarch/ | +10 | 0 replies | |
| 2/2 | KVM: x86: Do not use kvm_rip_read() unconditionally for KVM_PROFILINGarch/ | +2 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] KVM: x86: Correct use of kvm_rip_read()
Hi
Here are a couple of tweaks to dodge kvm_rip_read() in tracepoints and KVM_PROFILING when guest_state_protected.
This avoids, for example, hitting WARN_ON_ONCE in vt_cache_reg() for TDX VMs.
Adrian Hunter (2):
KVM: x86: Do not use kvm_rip_read() unconditionally in KVM tracepoints
KVM: x86: Do not use kvm_rip_read() unconditionally for KVM_PROFILING
arch/x86/kvm/trace.h | 13 ++++++++++--- arch/x86/kvm/x86.c | 3 ++- 2 files changed, 12 insertions(+), 4 deletions(-)
Regards
Adrian