From: Ingo Molnar <mingo@elte.hu>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Cliff Wickman <cpw@sgi.com>,
linux-kernel@vger.kernel.org, a.p.zijlstra@chello.nl,
paulus@samba.org
Subject: Re: [RFC] Performance Events 'Samples' report
Date: Fri, 25 Feb 2011 11:26:47 +0100 [thread overview]
Message-ID: <20110225102647.GA4228@elte.hu> (raw)
In-Reply-To: <20110225024014.GA16138@ghostprotocols.net>
* Arnaldo Carvalho de Melo <acme@ghostprotocols.net> wrote:
> Wasn't this fixed by:
>
> commit fec9cbd15b9e99bab9bc50f1ed7e20a1087d7c6d
> Author: Arnaldo Carvalho de Melo <acme@redhat.com>
> Date: Thu Feb 17 10:37:23 2011 -0200
>
> perf hists: Print number of samples, not the period sum
Yeah. I'll cherry-pick it over into perf/urgent, ok? It's been reported by several
people (I noticed it too) and the old numbers really made little sense - and the fix
is really simple.
Thanks,
Ingo
prev parent reply other threads:[~2011-02-25 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 0:15 [RFC] Performance Events 'Samples' report Cliff Wickman
2011-02-25 2:40 ` Arnaldo Carvalho de Melo
2011-02-25 10:26 ` Ingo Molnar [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=20110225102647.GA4228@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=cpw@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.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