From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: David Ahern <dsahern@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PEBS (in perf) stopped working from 3.6 -> 3.7
Date: Mon, 7 Jan 2013 15:40:00 +0100 [thread overview]
Message-ID: <20130107144000.GA8145@uio.no> (raw)
In-Reply-To: <50EA4594.9020309@gmail.com>
On Sun, Jan 06, 2013 at 08:48:36PM -0700, David Ahern wrote:
>> Why would the two be different?
> I will make a guess that is processor dependent. On an E5540 with
> 3.4.11-1.fc16.x86_64, 3.6.10-2.fc16.x86_64, and 3.8 I get the same
> failure message.
>
> But on a E5620, it works fine with 3.4 and 3.7 (no intermediate
> kernels on that box).
That sounds a bit odd; the CPU can certainly do it with 3.6.
/* Steinar */
--
Homepage: http://www.sesse.net/
prev parent reply other threads:[~2013-01-07 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 23:47 PEBS (in perf) stopped working from 3.6 -> 3.7 Steinar H. Gunderson
2013-01-05 0:16 ` David Ahern
2013-01-05 0:21 ` Steinar H. Gunderson
2013-01-05 1:05 ` Steinar H. Gunderson
2013-01-07 3:48 ` David Ahern
2013-01-07 14:40 ` Steinar H. Gunderson [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=20130107144000.GA8145@uio.no \
--to=sgunderson@bigfoot.com \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.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