[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250415104821.247234-1-adrian.hunter@intel.com>
Date: Tue, 15 Apr 2025 13:48:19 +0300
From: Adrian Hunter <adrian.hunter@...el.com>
To: pbonzini@...hat.com,
seanjc@...gle.com
Cc: kvm@...r.kernel.org,
rick.p.edgecombe@...el.com,
kirill.shutemov@...ux.intel.com,
kai.huang@...el.com,
reinette.chatre@...el.com,
xiaoyao.li@...el.com,
tony.lindgren@...ux.intel.com,
binbin.wu@...ux.intel.com,
isaku.yamahata@...el.com,
linux-kernel@...r.kernel.org,
yan.y.zhao@...el.com,
chao.gao@...el.com
Subject: [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
Powered by blists - more mailing lists