public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip] perf stat: define CHECK_ATTRS for easy attrs checking
Date: Tue, 30 Jun 2009 12:08:35 +0200	[thread overview]
Message-ID: <20090630100835.GE6942@elte.hu> (raw)
In-Reply-To: <1246274348.3018.3.camel@hpdv5.satnam>


* Jaswinder Singh Rajput <jaswinder@kernel.org> wrote:

> CHECK_ATTRS is useful :
>  1. for multiple attrs checking
>  2. avoid repetition of PERF_TYPE_ and PERF_COUNT_ and save space
>  3. avoids line breakage
> 
> Signed-off-by: Jaswinder Singh Rajput <jaswinderrajput@gmail.com>
> ---
>  tools/perf/builtin-stat.c |   18 ++++++++----------
>  1 files changed, 8 insertions(+), 10 deletions(-)
> 
> diff --git a/tools/perf/builtin-stat.c b/tools/perf/builtin-stat.c
> index 3e5ea4e..6231b39 100644
> --- a/tools/perf/builtin-stat.c
> +++ b/tools/perf/builtin-stat.c
> @@ -96,6 +96,10 @@ static u64			walltime_nsecs_noise;
>  static u64			runtime_cycles_avg;
>  static u64			runtime_cycles_noise;
>  
> +#define CHECK_ATTRS(t, c, counter)			\
> +	(attrs[counter].type == PERF_TYPE_##t &&	\
> +	 attrs[counter].config == PERF_COUNT_##c)

looks good except that the name should be something like 
MATCH_EVENT() not CHECK_ATTRS().

	Ingo

  reply	other threads:[~2009-06-30 10:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-29 11:19 [PATCH -tip] perf stat: define CHECK_ATTRS for easy attrs checking Jaswinder Singh Rajput
2009-06-30 10:08 ` Ingo Molnar [this message]
2009-06-30 13:09   ` 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=20090630100835.GE6942@elte.hu \
    --to=mingo@elte.hu \
    --cc=jaswinder@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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