From: Peter Zijlstra <peterz@infradead.org>
To: Andi Kleen <ak@linux.intel.com>
Cc: "Liang, Kan" <kan.liang@linux.intel.com>,
acme@redhat.com, linux-kernel@vger.kernel.org,
alexander.shishkin@linux.intel.com,
Jianfeng Gao <jianfeng.gao@intel.com>,
Andrew Cooper <Andrew.Cooper3@citrix.com>
Subject: Re: [RESEND PATCH] perf/x86/intel: Fix unchecked MSR access error for Alder Lake N
Date: Mon, 22 Aug 2022 17:47:03 +0200 [thread overview]
Message-ID: <YwOk991q0iBgcQWC@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <c09ba37c-f685-15a3-3042-8cb3a0f91282@linux.intel.com>
On Mon, Aug 22, 2022 at 05:08:55PM +0200, Andi Kleen wrote:
>
> > diff --git a/arch/x86/events/intel/core.c b/arch/x86/events/intel/core.c
> > index 2db93498ff71..232e24324fd7 100644
> > --- a/arch/x86/events/intel/core.c
> > +++ b/arch/x86/events/intel/core.c
> > @@ -4473,6 +4473,11 @@ static bool init_hybrid_pmu(int cpu)
> > struct x86_hybrid_pmu *pmu = NULL;
> > int i;
> > + if (boot_cpu_has(X86_FEATURE_HYPERVISOR)) {
> > + pr_warn_once("hybrid PMU and virt are incompatible\n");
> > + return false;
> > + }
>
> It's totally possible to virtualize hybrid correctly, so I don't think this
> is justified
With a magic incantation and a sacrificial chicken sure, but the typical
guest will not have it set up right and we'll get the kernel doing
*splat*.
So I'm going to keep this and then some virt person can provide us a new
flag for when they think the hypervisor did the right thing and exclude
themselves from this ban.
next prev parent reply other threads:[~2022-08-22 15:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 18:15 [RESEND PATCH] perf/x86/intel: Fix unchecked MSR access error for Alder Lake N kan.liang
2022-08-19 8:05 ` Peter Zijlstra
2022-08-19 8:33 ` Peter Zijlstra
2022-08-22 13:24 ` Liang, Kan
2022-08-22 13:55 ` Peter Zijlstra
2022-08-22 15:20 ` Liang, Kan
2022-08-19 14:38 ` Peter Zijlstra
2022-08-22 13:28 ` Liang, Kan
2022-08-22 13:48 ` Peter Zijlstra
2022-08-22 14:31 ` Andi Kleen
2022-08-22 14:39 ` Peter Zijlstra
2022-08-22 14:51 ` Andrew Cooper
2022-08-22 14:59 ` Liang, Kan
2022-08-22 15:21 ` Peter Zijlstra
2022-08-22 15:08 ` Andi Kleen
2022-08-22 15:47 ` Peter Zijlstra [this message]
2022-08-22 18:21 ` Sean Christopherson
2022-08-22 19:21 ` Andi Kleen
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=YwOk991q0iBgcQWC@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Andrew.Cooper3@citrix.com \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jianfeng.gao@intel.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
/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