From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Don Zickus <dzickus@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Stephane Eranian <eranian@google.com>,
Lin Ming <ming.m.lin@intel.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH -tip/perf/core] perf, x86: P4 PMU - Introduce event alias feature
Date: Thu, 21 Jul 2011 11:20:52 +0400 [thread overview]
Message-ID: <20110721072052.GM7492@sun> (raw)
In-Reply-To: <20110721064610.GB26260@elte.hu>
On Thu, Jul 21, 2011 at 08:46:10AM +0200, Ingo Molnar wrote:
...
>
> > + */
> > +struct p4_event_alias {
> > + u64 orig;
> > + u64 alter;
>
> what is an 'alter'? alias? alternate?
Shorthanded 'alternate', I can change it to alias.
>
> > +} p4_event_aliases[] = {
> > + {
> > + /*
> > + * Non-halted cycles can be substituted with
> > + * non-sleeping cycles (see Intel SDM Vol3b for
> > + * details).
> > + */
> > + .orig =
> > + p4_config_pack_escr(P4_ESCR_EVENT(P4_EVENT_GLOBAL_POWER_EVENTS) |
> > + P4_ESCR_EMASK_BIT(P4_EVENT_GLOBAL_POWER_EVENTS, RUNNING)),
> > + .alter =
> > + p4_config_pack_escr(P4_ESCR_EVENT(P4_EVENT_EXECUTION_EVENT) |
> > + P4_ESCR_EMASK_BIT(P4_EVENT_EXECUTION_EVENT, NBOGUS0)|
> > + P4_ESCR_EMASK_BIT(P4_EVENT_EXECUTION_EVENT, NBOGUS1)|
> > + P4_ESCR_EMASK_BIT(P4_EVENT_EXECUTION_EVENT, NBOGUS2)|
> > + P4_ESCR_EMASK_BIT(P4_EVENT_EXECUTION_EVENT, NBOGUS3)|
> > + P4_ESCR_EMASK_BIT(P4_EVENT_EXECUTION_EVENT, BOGUS0) |
> > + P4_ESCR_EMASK_BIT(P4_EVENT_EXECUTION_EVENT, BOGUS1) |
> > + P4_ESCR_EMASK_BIT(P4_EVENT_EXECUTION_EVENT, BOGUS2) |
> > + P4_ESCR_EMASK_BIT(P4_EVENT_EXECUTION_EVENT, BOGUS3))|
> > + p4_config_pack_cccr(P4_CCCR_THRESHOLD(15) | P4_CCCR_COMPLEMENT |
> > + P4_CCCR_COMPARE),
>
> That currently we only offer an alias for the generic cycles event is
> an important property - yet it's only visible from the code and is
> not mentioned in any of the voluminous comments. Good comments are to
> the point and focused: what problem is being solved, how is it solved
> and what are the limitations of the solution.
ok, will update the comment.
>
> > + },
> > +};
> > +
> > +static u64 p4_get_alias_event(u64 config)
> > +{
> > + u64 config_match;
> > + int i;
> > +
> > + /*
> > + * Probably we're lucky and don't have to do
> > + * matching over all config bits.
> > + */
> > + if (!(config & P4_CONFIG_ALIASABLE))
> > + return 0;
>
> 'all' config bits? There's a single alias mapping in
> p4_event_aliases[] right now which makes the comment rather
> misleading ...
no, the cycle below does check for all bits in config, and test
for single bit might help us to return early.
>
> > +
> > + config_match = config & P4_CONFIG_EVENT_ALIAS_MASK;
> > +
> > + /*
> > + * If an event was previously swapped to the alter config
> > + * we should swap it back otherwise contnention on registers
> > + * will return back.
>
> 'alter config' is a new English word apparently. We can invent new
> words but is it really warranted here? 'alternate config'? 'config
> alias'?
i'll update to alternate config
>
> > + */
> > + for (i = 0; i < ARRAY_SIZE(p4_event_aliases); i++) {
> > + if (config_match == p4_event_aliases[i].orig) {
> > + config_match = p4_event_aliases[i].alter;
> > + break;
> > + } else if (config_match == p4_event_aliases[i].alter) {
> > + config_match = p4_event_aliases[i].orig;
> > + break;
> > + }
> > + }
>
> Since this .c file is P4 specific and p4_event_aliases[] is a
> file-scope array, is the p4_ prefix even needed?
I prefer them to be distinguished this way, since the .c file in
real is included into another (perf_event.c) file.
>
> > +
> > + if (i >= ARRAY_SIZE(p4_event_aliases))
> > + return 0;
> > +
> > + return (config_match |
> > + (config & P4_CONFIG_EVENT_ALIAS_IMMUTABLE_BITS));
>
> 'return' is not a function. Also, please don't break the line
> pointlessly.
It is perfectly fine to return args in braces,
but I will change it.
...
> > + /*
> > + * Probably an event alias is still available.
>
> s/Probably/Possibly?
Hm? I don't get what is wrong with 'probably'.
...
> >
> > /* Try to register using hardware perf events */
> > event = perf_event_create_kernel_counter(wd_attr, cpu, NULL, watchdog_overflow_callback, NULL);
>
> This looks like the right approach otherwise. Peter?
>
> Thanks,
>
> Ingo
Thanks Ingo, I'll update the patch.
Cyrill
next prev parent reply other threads:[~2011-07-21 7:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 20:17 [PATCH -tip/perf/core] perf, x86: P4 PMU - Introduce event alias feature Cyrill Gorcunov
2011-07-14 18:46 ` Don Zickus
2011-07-21 6:46 ` Ingo Molnar
2011-07-21 7:20 ` Cyrill Gorcunov [this message]
2011-07-21 7:52 ` Ingo Molnar
2011-07-21 8:07 ` Cyrill Gorcunov
2011-07-21 8:15 ` Ingo Molnar
2011-07-21 12:02 ` Peter Zijlstra
2011-07-21 10:00 ` [tip:perf/core] " tip-bot for Cyrill Gorcunov
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=20110721072052.GM7492@sun \
--to=gorcunov@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=dzickus@redhat.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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