From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Borislav Petkov <bp@alien8.de>, Amy Wiles <amy.l.wiles@intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
Jacob Pan <jacob.jun.pan@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] x86/rapl: Do not load in a guest
Date: Fri, 4 Dec 2015 09:28:23 +0100 [thread overview]
Message-ID: <20151204082823.GA31591@gmail.com> (raw)
In-Reply-To: <20151204082256.GC17308@twins.programming.kicks-ass.net>
* Peter Zijlstra <peterz@infradead.org> wrote:
> On Fri, Dec 04, 2015 at 08:42:06AM +0100, Ingo Molnar wrote:
> >
> > * Borislav Petkov <bp@alien8.de> wrote:
> >
> > > From: Borislav Petkov <bp@suse.de>
> > >
> > > qemu/kvm doesn't support RAPL and RAPL doesn't have a CPUID feature bit
> > > so check whether we're in a guest instead.
> >
> > So when a hypervisor starts supporting RAPL we'll disable the driver erroneously?
> >
> > Isn't there any better method to detect RAPL support?
> >
> > So in particular in drivers/powercap/intel_rapl.c there's an enumerated list of
> > CPU models, which is used via a x86_match_cpu() call. That's still not ideal (it
> > does not work on hypervisors for example), but even better would be to detect RAPL
> > support in some other fashion, that does not rely on us statically enumerating CPU
> > models that support it.
>
> RAPL isn't enumerated, the best we could do is attempt to write to one
> of the writable MSRs and see if that 'works'.
Hm, bad - writing to MSRs like that is generally dangerous.
So we should at least provide a central 'is RAPL available' call instead of
spreading multiple X86_FEATURE_HYPERVISOR checks.
Thanks,
Ingo
next prev parent reply other threads:[~2015-12-04 8:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 18:27 [PATCH] x86/rapl: Do not load in a guest Borislav Petkov
2015-12-03 18:38 ` Jacob Pan
2015-12-03 18:42 ` Borislav Petkov
2015-12-03 18:59 ` Jacob Pan
2015-12-03 23:32 ` Rafael J. Wysocki
2015-12-03 23:25 ` Borislav Petkov
2015-12-04 1:00 ` Rafael J. Wysocki
2015-12-04 7:42 ` Ingo Molnar
2015-12-04 8:22 ` Peter Zijlstra
2015-12-04 8:28 ` Ingo Molnar [this message]
2015-12-04 10:19 ` Borislav Petkov
2015-12-04 10:41 ` Paolo Bonzini
2015-12-04 10:56 ` Borislav Petkov
2015-12-04 11:53 ` Ingo Molnar
2015-12-04 17:46 ` Jacob Pan
2015-12-04 17:52 ` Paolo Bonzini
2015-12-04 18:04 ` Borislav Petkov
2015-12-04 18:16 ` Jacob Pan
2015-12-04 18:28 ` Borislav Petkov
2015-12-04 18:37 ` Jacob Pan
2015-12-04 19:41 ` Borislav Petkov
2015-12-04 17:51 ` Jacob Pan
2015-12-04 22:14 ` Peter Zijlstra
2015-12-04 22:39 ` H. Peter Anvin
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=20151204082823.GA31591@gmail.com \
--to=mingo@kernel.org \
--cc=acme@kernel.org \
--cc=amy.l.wiles@intel.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=tglx@linutronix.de \
/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