public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@linux.intel.com>
To: David Ahern <dsahern@gmail.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Maarten Lankhorst <m.b.lankhorst@gmail.com>,
	x86@kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Stephane Eranian <eranian@google.com>
Subject: Re: perf, x86: Disable PEBS on SandyBridge chips
Date: Fri, 17 Feb 2012 14:12:17 -0800	[thread overview]
Message-ID: <4F3ED0C1.80907@linux.intel.com> (raw)
In-Reply-To: <4F3ECFC7.4010607@gmail.com>

On 02/17/2012 02:08 PM, David Ahern wrote:
> On 2/17/12 2:40 PM, H. Peter Anvin wrote:
>> On 02/17/2012 07:12 AM, Peter Zijlstra wrote:
>>> On Fri, 2012-02-17 at 13:39 +0100, Maarten Lankhorst wrote:
>>>> Hey Peter,
>>>>
>>>> Why is PEBS disabled? If I look at the intel_clovertown_quirks I can
>>>> see
>>>> why it's disabled for that cpu, but the sandy bridge one lacks any kind
>>>> of clarification or information on why, or how I can learn more.
>>>
>>> hpa, could you get the official Intel answer on this?
>>
>> *Where* is PEBS disabled?
>
> arch/x86/kernel/cpu/perf_event_intel.c,
> intel_sandybridge_quirk()
>

OK, this is Peter's patch and I don't think I was involved with it... I 
need more of a pointer to be able to track this down.

	-hpa



      reply	other threads:[~2012-02-17 22:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-17 12:39 perf, x86: Disable PEBS on SandyBridge chips Maarten Lankhorst
2012-02-17 15:12 ` Peter Zijlstra
2012-02-17 21:40   ` H. Peter Anvin
2012-02-17 22:08     ` David Ahern
2012-02-17 22:12       ` H. Peter Anvin [this message]

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=4F3ED0C1.80907@linux.intel.com \
    --to=hpa@linux.intel.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=dsahern@gmail.com \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.b.lankhorst@gmail.com \
    --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