From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip] perf_counter tools: shorten names for events
Date: Wed, 24 Jun 2009 04:29:52 +0530 [thread overview]
Message-ID: <1245797992.4954.5.camel@localhost.localdomain> (raw)
In-Reply-To: <1245795173.26280.17.camel@localhost.localdomain>
On Wed, 2009-06-24 at 03:42 +0530, Jaswinder Singh Rajput wrote:
> > Note, branches are special - we dont really have 'branch loads',
> > branches are executions. 'Branches' and 'Branch-misses' are the
> > right term.
> >
> > Do you agree?
> >
>
> Event we used for (BPU, READ, ACCESS) is 'branch instructions retired'
>
> So 'branch loads' we mean 'branch instruction loaded and retired'
>
> I like all of them : 'branch loads', 'branch retired' or 'branches'
>
> Please let me know, which one is best option so that I can prepare the
> patch.
>
Or if branches is special and following values are always invalid :
(BPU, WRITE, ACCESS)
(BPU, WRITE, MISS)
(BPU, PREFETCH, ACCESS)
(BPU, PREFTECH, MISS)
then can we move BPU to some other category from Hardware cache
counters.
Thanks,
--
JSR
next prev parent reply other threads:[~2009-06-23 23:00 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 12:28 [PATCH -tip] perf_counter tools: shorten names for events Jaswinder Singh Rajput
2009-06-23 13:52 ` Jaswinder Singh Rajput
2009-06-23 19:56 ` Ingo Molnar
2009-06-23 22:12 ` Jaswinder Singh Rajput
2009-06-23 22:59 ` Jaswinder Singh Rajput [this message]
2009-06-24 8:40 ` Ingo Molnar
2009-06-24 17:59 ` Jaswinder Singh Rajput
2009-06-24 18:07 ` Ingo Molnar
2009-06-24 18:18 ` Jaswinder Singh Rajput
2009-06-24 20:41 ` Jaswinder Singh Rajput
2009-06-24 21:00 ` Thomas Gleixner
2009-06-25 4:29 ` Jaswinder Singh Rajput
2009-06-25 4:34 ` Roland Dreier
2009-06-25 9:22 ` Ingo Molnar
2009-06-25 9:24 ` Ingo Molnar
2009-06-25 12:48 ` Thomas Gleixner
2009-06-25 13:23 ` Jaswinder Singh Rajput
2009-06-25 15:05 ` Roland Dreier
2009-06-25 15:11 ` Jaswinder Singh Rajput
2009-06-25 15:03 ` Roland Dreier
2009-06-25 15:24 ` Ingo Molnar
2009-06-25 9:33 ` Ingo Molnar
2009-06-25 12:55 ` Jaswinder Singh Rajput
2009-06-25 15:09 ` Roland Dreier
2009-06-25 15:26 ` Ingo Molnar
2009-06-25 15:34 ` Ingo Molnar
2009-06-26 16:06 ` Jaswinder Singh Rajput
2009-06-26 18:47 ` Ingo Molnar
2009-07-05 0:25 ` Anton Blanchard
2009-07-05 0:32 ` Ingo Molnar
2009-07-06 12:01 ` [PATCH] perf_counter tools: Rename cache events to remove $ Anton Blanchard
2009-07-10 10:39 ` [tip:perfcounters/core] " tip-bot for Anton Blanchard
2009-06-25 15:33 ` [tip:perfcounters/urgent] perf_counter tools: Shorten names for events tip-bot for Jaswinder Singh Rajput
2009-06-25 15:57 ` Jaswinder Singh Rajput
2009-06-25 19:55 ` Ingo Molnar
2009-06-25 19:57 ` [tip:perfcounters/urgent] perf_counter tools: Add alias for 'l1d' and 'l1i' tip-bot for Jaswinder Singh Rajput
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=1245797992.4954.5.camel@localhost.localdomain \
--to=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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