From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Borislav Petkov <bp@amd64.org>
Cc: Arnaldo Carvalho de Melo <acme@infradead.org>,
Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Funny perf
Date: Wed, 23 Feb 2011 11:21:48 +0100 [thread overview]
Message-ID: <1298456508.2217.357.camel@twins> (raw)
In-Reply-To: <20110217182658.GA23443@aftab>
On Thu, 2011-02-17 at 19:26 +0100, Borislav Petkov wrote:
>
> so this looks like some of the samples do not belong in the perf.data
> output with that garbled cpu field. It lets me also assume that the
> sample->time field is also crap so the timestamp check is falsely
> tripped.
Most interesting, I haven't tried to reproduce, but it does sound
smelly.
I did have a quick peek at some code I suspected but that all seems in
order. I guess someone will have to sit down and figure this out proper,
if nobody steps up I guess it'll have to be me, but that also means it
might take a while since I've got some other pending stuff to stare at
before this :/
next prev parent reply other threads:[~2011-02-23 10:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 18:26 Funny perf Borislav Petkov
2011-02-23 10:21 ` Peter Zijlstra [this message]
2011-02-23 11:53 ` Arnaldo Carvalho de Melo
2011-02-23 12:29 ` Borislav Petkov
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=1298456508.2217.357.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=acme@infradead.org \
--cc=bp@amd64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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