mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Matt Domsch <Matt_Domsch@dell.com>
Cc: Arjan van de Ven <arjan@linux.intel.com>,
	Ingo Molnar <mingo@elte.hu>,
	Stephane Eranian <eranian@google.com>,
	"robert.richter" <robert.richter@amd.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"H. Peter Anvin" <hpa@linux.kernel.org>
Subject: Re: [PATCH] perf, x86: Disable perf if the BIOS got its grubby paws on the PMU
Date: Fri, 03 Sep 2010 16:46:03 +0200	[thread overview]
Message-ID: <1283525163.2050.105.camel@laptop> (raw)
In-Reply-To: <20100903143258.GB373@auslistsprd01.us.dell.com>

On Fri, 2010-09-03 at 09:32 -0500, Matt Domsch wrote:
> On Fri, Sep 03, 2010 at 06:53:59AM -0700, Arjan van de Ven wrote:
> > On 9/3/2010 2:13 AM, Peter Zijlstra wrote:
> > >
> > >+static void print_BIOS_fail(void)
> > >+{
> > >+	printk(KERN_ERR "\n");
> > >+	printk(KERN_ERR "=============================================\n");
> > >+	printk(KERN_ERR "It appears the BIOS is actively using the PMU\n");
> > >+	printk(KERN_ERR "this avoids Linux from using it, please de-  \n");
> > >+	printk(KERN_ERR "activate this BIOS feature or request a BIOS \n");
> > >+	printk(KERN_ERR "update from your vendor.                     \n");
> > >+	printk(KERN_ERR "=============================================\n");
> > >+
> > >+	memset(&x86_pmu, 0, sizeof(x86_pmu));
> > >+}

> I must object to messages that repeatedly (at least on every boot)
> tell system administrators to contact their hardware vendor's support
> lines, when it's not clear what the BIOS is doing is incorrect. 

It is using the PMU, it should not _ever_ do that.

>  There
> are plenty of valid reasons why BIOS itself would use PMU counters.
> Dell PowerEdge server power management, handled by the BIOS, certainly
> does use one.

Them make them stop doing that, or at least provide a BIOS option to
disable this Feat^WFailure-add.

An no, doing power-management from the BIOS is most certainly not a
valid reason. That's not what BIOSes are for, a BIOS should bring up the
system and then sod off.

> My understanding is that there is a mechanism for the OS to request
> BIOS to release use of PMU counters.  Are we doing that?

I'm not aware of any such thing. The Intel Arch docs most certainly
don't specify anything about that.

>   If BIOS does
> not release the counters when asked, ok, that's something to
> (potentially) warn about.  But blanket "BIOS is using a CPU feature!
> Bad BIOS!  No treat for you!" - that's not helpful to anyone.

Again, I'm not aware there is a spec on how to ask anything of the BIOS,
let alone a part pertaining to PMU functionality.

  reply	other threads:[~2010-09-03 14:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-03  9:13 Peter Zijlstra
2010-09-03 13:53 ` Arjan van de Ven
2010-09-03 14:32   ` Matt Domsch
2010-09-03 14:46     ` Peter Zijlstra [this message]
2010-09-07 15:15       ` Robert Richter
2010-09-07 16:51         ` Robert Richter

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=1283525163.2050.105.camel@laptop \
    --to=peterz@infradead.org \
    --cc=Matt_Domsch@dell.com \
    --cc=arjan@linux.intel.com \
    --cc=eranian@google.com \
    --cc=hpa@linux.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=robert.richter@amd.com \
    --cc=torvalds@linux-foundation.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

Powered by JetHome