From: Adrian Hunter <adrian.hunter@intel.com>
To: pbonzini@redhat.com, seanjc@google.com
Cc: kvm@vger.kernel.org, rick.p.edgecombe@intel.com,
kirill.shutemov@linux.intel.com, kai.huang@intel.com,
reinette.chatre@intel.com, xiaoyao.li@intel.com,
tony.lindgren@linux.intel.com, binbin.wu@linux.intel.com,
isaku.yamahata@intel.com, linux-kernel@vger.kernel.org,
yan.y.zhao@intel.com, chao.gao@intel.com
Subject: [PATCH 0/2] KVM: x86: Correct use of kvm_rip_read()
Date: Tue, 15 Apr 2025 13:48:19 +0300 [thread overview]
Message-ID: <20250415104821.247234-1-adrian.hunter@intel.com> (raw)
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
next reply other threads:[~2025-04-15 10:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 10:48 Adrian Hunter [this message]
2025-04-15 10:48 ` [PATCH 1/2] KVM: x86: Do not use kvm_rip_read() unconditionally in KVM tracepoints Adrian Hunter
2025-04-15 10:48 ` [PATCH 2/2] KVM: x86: Do not use kvm_rip_read() unconditionally for KVM_PROFILING Adrian Hunter
2025-04-15 11:31 ` [PATCH 0/2] KVM: x86: Correct use of kvm_rip_read() Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250415104821.247234-1-adrian.hunter@intel.com \
--to=adrian.hunter@intel.com \
--cc=binbin.wu@linux.intel.com \
--cc=chao.gao@intel.com \
--cc=isaku.yamahata@intel.com \
--cc=kai.huang@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=reinette.chatre@intel.com \
--cc=rick.p.edgecombe@intel.com \
--cc=seanjc@google.com \
--cc=tony.lindgren@linux.intel.com \
--cc=xiaoyao.li@intel.com \
--cc=yan.y.zhao@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox