From: Benjamin Moody <benjamin.moody@gmail.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Bizarre results from perf event API
Date: Mon, 23 Feb 2015 23:13:24 +0000 [thread overview]
Message-ID: <CAAk6P0W6MAV2Vi1HuFXJBKnpvo7W8UzFGtHgKsyTEYFbCeD05Q@mail.gmail.com> (raw)
In-Reply-To: <87sidwuzmf.fsf@tassilo.jf.intel.com>
On 2/23/15, Andi Kleen <andi@firstfloor.org> wrote:
> Benjamin Moody <benjamin.moody@gmail.com> writes:
>>
>> pe.pinned = 1; /* always track */
>
> You definitely don't want pinned
I'm fairly confident that I do, actually, but why do you say that?
In any case, these problems occur regardless of pinned-ness.
Benjamin
prev parent reply other threads:[~2015-02-23 23:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 23:26 Bizarre results from perf event API Benjamin Moody
2015-02-21 0:39 ` David Ahern
2015-02-21 21:44 ` Benjamin Moody
2015-02-21 22:59 ` Vince Weaver
2015-02-22 20:12 ` Benjamin Moody
2015-02-22 20:37 ` Vince Weaver
2015-02-24 0:46 ` Benjamin Moody
2015-02-24 1:21 ` David Ahern
2015-02-27 21:41 ` Benjamin Moody
2015-02-23 20:44 ` Andi Kleen
2015-02-23 23:13 ` Benjamin Moody [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=CAAk6P0W6MAV2Vi1HuFXJBKnpvo7W8UzFGtHgKsyTEYFbCeD05Q@mail.gmail.com \
--to=benjamin.moody@gmail.com \
--cc=andi@firstfloor.org \
--cc=linux-perf-users@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;
as well as URLs for NNTP newsgroup(s).