From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: "Yan, Zheng" <zheng.z.yan@intel.com>,
eranian@google.com, mingo@elte.hu, andi@firstfloor.org,
avi@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf/x86: Disable uncore on virtualized CPU.
Date: Wed, 5 Sep 2012 11:08:39 +0200 [thread overview]
Message-ID: <20120905090839.GA31992@gmail.com> (raw)
In-Reply-To: <1346834836.2600.3.camel@twins>
* Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> On Wed, 2012-09-05 at 08:35 +0200, Ingo Molnar wrote:
> > * Yan, Zheng <zheng.z.yan@intel.com> wrote:
> >
> > > From: "Yan, Zheng" <zheng.z.yan@intel.com>
> > >
> > > Initializing uncore PMU on virtualized CPU may hang the kernel.
> > > This is because kvm does not emulate the entire hardware. Thers
> > > are lots of uncore related MSRs, making kvm enumerate them all
> > > is a non-trival task. So just disable uncore on virtualized CPU.
> > >
> > > Signed-off-by: Yan, Zheng <zheng.z.yan@intel.com>
> > > ---
> > > arch/x86/kernel/cpu/perf_event_intel_uncore.c | 3 +++
> > > 1 file changed, 3 insertions(+)
> > >
> > > diff --git a/arch/x86/kernel/cpu/perf_event_intel_uncore.c b/arch/x86/kernel/cpu/perf_event_intel_uncore.c
> > > index 0a55710..2f005ba 100644
> > > --- a/arch/x86/kernel/cpu/perf_event_intel_uncore.c
> > > +++ b/arch/x86/kernel/cpu/perf_event_intel_uncore.c
> > > @@ -2898,6 +2898,9 @@ static int __init intel_uncore_init(void)
> > > if (boot_cpu_data.x86_vendor != X86_VENDOR_INTEL)
> > > return -ENODEV;
> > >
> > > + if (cpu_has_hypervisor)
> > > + return -ENODEV;
> > > +
> > > ret = uncore_pci_init();
> > > if (ret)
> > > goto fail;
> >
> > Cannot the presence of the uncore hardware be detected in a
> > cleaner fashion, via the PCI config space and such?
>
> No, part of the uncore PMUs are in MSR space and aren't
> discoverable. CPUID model checks + hard assumptions of
> presence are all that we are left with.
>
> Now Avi suggested we teach KVM about these MSRs and then
> modify the uncore driver to test if the MSRs actually work --
> as in retain values written to them and aren't always 0.
>
> That's a larger patch though, partly because enumerating the
> gazillion MSRs consumed by the various uncore PMUs is a
> tedious job, and we can always do this later.
>
> This patch is a minimal patch to at least make things 'work'
> for now.
Ok, no objections.
Thanks,
Ingo
next prev parent reply other threads:[~2012-09-05 9:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 9:08 [PATCH] perf/x86: Disable uncore on virtualized CPU Yan, Zheng
2012-08-21 12:55 ` Pekka Enberg
2012-08-31 7:12 ` Pekka Enberg
2012-08-21 14:31 ` Andi Kleen
2012-08-21 14:42 ` Pekka Enberg
2012-09-05 6:35 ` Ingo Molnar
2012-09-05 8:47 ` Peter Zijlstra
2012-09-05 9:08 ` Ingo Molnar [this message]
2012-09-05 18:52 ` Andi Kleen
2012-10-20 8:23 ` [tip:perf/urgent] perf/x86: Disable uncore on virtualized CPUs tip-bot for Yan, Zheng
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=20120905090839.GA31992@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=avi@redhat.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=zheng.z.yan@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