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 stat: memcpy is only required if no event is selected and !null_run
Date: Sun, 28 Jun 2009 11:01:29 +0530 [thread overview]
Message-ID: <1246167089.4497.8.camel@hpdv5.satnam> (raw)
In-Reply-To: <1246126749.32198.16.camel@hpdv5.satnam>
If You want can also add Impact Line.
Impact: Speedup, reduce binary size.
On Sat, 2009-06-27 at 23:49 +0530, Jaswinder Singh Rajput wrote:
> Set attrs and nr_counters if no event is selected and !null_run
>
> Setting of attrs should depend on number of counters,
> so we need to memcpy only for sizeof(default_attrs)
>
> and set nr_counters as ARRAY_SIZE(default_attrs) in place of hardcoded value
>
> Signed-off-by: Jaswinder Singh Rajput <jaswinderrajput@gmail.com>
> ---
> tools/perf/builtin-stat.c | 11 ++++++-----
> 1 files changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/tools/perf/builtin-stat.c b/tools/perf/builtin-stat.c
> index 3840a70..3e5ea4e 100644
> --- a/tools/perf/builtin-stat.c
> +++ b/tools/perf/builtin-stat.c
> @@ -46,7 +46,7 @@
> #include <sys/prctl.h>
> #include <math.h>
>
> -static struct perf_counter_attr default_attrs[MAX_COUNTERS] = {
> +static struct perf_counter_attr default_attrs[] = {
>
> { .type = PERF_TYPE_SOFTWARE, .config = PERF_COUNT_SW_TASK_CLOCK },
> { .type = PERF_TYPE_SOFTWARE, .config = PERF_COUNT_SW_CONTEXT_SWITCHES},
> @@ -477,16 +477,17 @@ int cmd_stat(int argc, const char **argv, const char *prefix)
> {
> int status;
>
> - memcpy(attrs, default_attrs, sizeof(attrs));
> -
> argc = parse_options(argc, argv, options, stat_usage, 0);
> if (!argc)
> usage_with_options(stat_usage, options);
> if (run_count <= 0 || run_count > MAX_RUN)
> usage_with_options(stat_usage, options);
>
> - if (!null_run && !nr_counters)
> - nr_counters = 8;
> + /* Set attrs and nr_counters if no event is selected and !null_run */
> + if (!null_run && !nr_counters) {
> + memcpy(attrs, default_attrs, sizeof(default_attrs));
> + nr_counters = ARRAY_SIZE(default_attrs);
> + }
>
> nr_cpus = sysconf(_SC_NPROCESSORS_ONLN);
> assert(nr_cpus <= MAX_NR_CPUS);
next prev parent reply other threads:[~2009-06-28 5:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-27 18:19 Jaswinder Singh Rajput
2009-06-28 5:31 ` Jaswinder Singh Rajput [this message]
2009-06-28 13:42 ` [tip:perfcounters/urgent] perf stat: Micro-optimize the code: " 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=1246167089.4497.8.camel@hpdv5.satnam \
--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
all inboxes | Powered by JetHome®