From: Andi Kleen <ak@linux.intel.com>
To: "Liang, Kan" <kan.liang@linux.intel.com>,
Sean Christopherson <seanjc@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Jianfeng Gao <jianfeng.gao@intel.com>,
Andrew Cooper <Andrew.Cooper3@citrix.com>
Subject: Re: [PATCH] perf/x86: KVM: Disable vPMU support on hybrid CPUs (host PMUs)
Date: Mon, 23 Jan 2023 17:04:33 -0800 [thread overview]
Message-ID: <67facb87-f835-abcd-3d1b-527531b26e52@linux.intel.com> (raw)
In-Reply-To: <e161b7c0-f0be-23c8-9a25-002260c2a085@linux.intel.com>
> If I understand correct, the workaround in KVM is to add a white/black
> list to filter the events. I think we can do the same thing for the
> hybrid machine for now.
> https://lore.kernel.org/lkml/CAOyeoRUUK+T_71J=+zcToyL93LkpARpsuWSfZS7jbJq=wd1rQg@mail.gmail.com/
This will make everyone who actually wants to use the PMU sad.
It's reasonable if the vCPUs are not bound, but if they are bound it
would be better to expose it with a suitable CPUID for the types.
-Andi
next prev parent reply other threads:[~2023-01-24 1:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 0:40 [PATCH] perf/x86: KVM: Disable vPMU support on hybrid CPUs (host PMUs) Sean Christopherson
2023-01-20 14:39 ` Liang, Kan
2023-01-20 17:32 ` Sean Christopherson
2023-01-20 19:55 ` Liang, Kan
2023-01-20 20:34 ` Sean Christopherson
2023-01-20 22:00 ` Liang, Kan
2023-01-24 1:04 ` Andi Kleen [this message]
2023-01-24 15:31 ` Liang, Kan
2023-01-31 10:59 ` Peter Zijlstra
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=67facb87-f835-abcd-3d1b-527531b26e52@linux.intel.com \
--to=ak@linux.intel.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jianfeng.gao@intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).