From: Sean Christopherson <seanjc@google.com>
To: Like Xu <like.xu@linux.intel.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: x86/pt: Do not inject TraceToPAPMI when guest PT isn't supported
Date: Wed, 26 May 2021 17:38:57 +0000 [thread overview]
Message-ID: <YK6HsR4QXbVuhZf8@google.com> (raw)
In-Reply-To: <20210514084436.848396-1-like.xu@linux.intel.com>
On Fri, May 14, 2021, Like Xu wrote:
> When a PT perf user is running in system-wide mode on the host,
> the guest (w/ pt_mode=0) will warn about anonymous NMIs from
> kvm_handle_intel_pt_intr():
>
> [ 18.126444] Uhhuh. NMI received for unknown reason 10 on CPU 0.
> [ 18.126447] Do you have a strange power saving mode enabled?
> [ 18.126448] Dazed and confused, but trying to continue
>
> In this case, these PMIs should be handled by the host PT handler().
> When PT is used in guest-only mode, it's harmless to call host handler.
>
> Fix: 8479e04e7d("KVM: x86: Inject PMI for KVM guest")
s/Fix/Fixes
> Signed-off-by: Like Xu <like.xu@linux.intel.com>
> ---
> arch/x86/events/intel/core.c | 3 +--
> arch/x86/kvm/x86.c | 3 +++
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/events/intel/core.c b/arch/x86/events/intel/core.c
> index 2521d03de5e0..2f09eb0853de 100644
> --- a/arch/x86/events/intel/core.c
> +++ b/arch/x86/events/intel/core.c
> @@ -2853,8 +2853,7 @@ static int handle_pmi_common(struct pt_regs *regs, u64 status)
> if (unlikely(perf_guest_cbs && perf_guest_cbs->is_in_guest() &&
> perf_guest_cbs->handle_intel_pt_intr))
> perf_guest_cbs->handle_intel_pt_intr();
> - else
> - intel_pt_interrupt();
> + intel_pt_interrupt();
Would it make sense to instead do something like:
bool host_pmi = true;
...
if (unlikely(perf_guest_cbs && perf_guest_cbs->is_in_guest() &&
perf_guest_cbs->handle_intel_pt_intr)
host_pmi = !perf_guest_cbs->handle_intel_pt_intr();
if (likely(host_pmi))
intel_pt_interrupt();
> }
>
> /*
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index 6529e2023147..6660f3948cea 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -8087,6 +8087,9 @@ static void kvm_handle_intel_pt_intr(void)
> {
> struct kvm_vcpu *vcpu = __this_cpu_read(current_vcpu);
>
> + if (!guest_cpuid_has(vcpu, X86_FEATURE_INTEL_PT))
> + return;
> +
> kvm_make_request(KVM_REQ_PMI, vcpu);
> __set_bit(MSR_CORE_PERF_GLOBAL_OVF_CTRL_TRACE_TOPA_PMI_BIT,
> (unsigned long *)&vcpu->arch.pmu.global_status);
> --
> 2.31.1
>
next prev parent reply other threads:[~2021-05-26 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 8:44 [PATCH] KVM: x86/pt: Do not inject TraceToPAPMI when guest PT isn't supported Like Xu
2021-05-26 17:38 ` Sean Christopherson [this message]
2021-06-21 4:03 ` Like Xu
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=YK6HsR4QXbVuhZf8@google.com \
--to=seanjc@google.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=like.xu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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