From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Mike Galbraith <efault@gmx.de>
Subject: Re: [PATCH 2/2] perf tools: Add a general option to enable raw sample records
Date: Fri, 14 Aug 2009 12:07:22 +0200 [thread overview]
Message-ID: <20090814100721.GB5992@nowhere> (raw)
In-Reply-To: <1250244300-6343-3-git-send-email-fweisbec@gmail.com>
Sorry, please ignore this one, it has been resent by mistake :-(
On Fri, Aug 14, 2009 at 12:05:00PM +0200, Frederic Weisbecker wrote:
> While we can enable the perf sample records per tracepoint counter,
> we may also want to enable this option for every tracepoint
> counters to open, so that we don't need to add a :record flag
> for all of them.
>
> Add the -R, --raw-samples options for this purpose.
>
> Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
> Cc: Mike Galbraith <efault@gmx.de>
> ---
> tools/perf/builtin-record.c | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
> index 3be0301..e67c4fa 100644
> --- a/tools/perf/builtin-record.c
> +++ b/tools/perf/builtin-record.c
> @@ -35,6 +35,7 @@ static int output;
> static const char *output_name = "perf.data";
> static int group = 0;
> static unsigned int realtime_prio = 0;
> +static int raw_samples = 0;
> static int system_wide = 0;
> static int profile_cpu = -1;
> static pid_t target_pid = -1;
> @@ -400,6 +401,8 @@ static void create_counter(int counter, int cpu, pid_t pid)
> if (call_graph)
> attr->sample_type |= PERF_SAMPLE_CALLCHAIN;
>
> + if (raw_samples)
> + attr->sample_type |= PERF_SAMPLE_RAW;
>
> attr->mmap = track;
> attr->comm = track;
> @@ -632,6 +635,8 @@ static const struct option options[] = {
> "record events on existing pid"),
> OPT_INTEGER('r', "realtime", &realtime_prio,
> "collect data with this RT SCHED_FIFO priority"),
> + OPT_BOOLEAN('R', "raw-samples", &raw_samples,
> + "collect raw sample records from all opened counters"),
> OPT_BOOLEAN('a', "all-cpus", &system_wide,
> "system-wide collection from all CPUs"),
> OPT_BOOLEAN('A', "append", &append_file,
> --
> 1.6.2.3
>
next prev parent reply other threads:[~2009-08-14 10:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 10:04 [PATCH 1/2] perf tools: Add a per tracepoint counter attribute to get raw sample Frederic Weisbecker
2009-08-14 10:04 ` [PATCH] perf tools: Factorize the thread code in a dedicated file Frederic Weisbecker
2009-08-14 10:21 ` [PATCH v2] " Frederic Weisbecker
2009-08-15 14:12 ` [tip:perfcounters/core] " tip-bot for Frederic Weisbecker
2009-08-14 10:05 ` [PATCH 2/2] perf tools: Add a general option to enable raw sample records Frederic Weisbecker
2009-08-14 10:07 ` Frederic Weisbecker [this message]
2009-08-14 10:07 ` [PATCH 1/2] perf tools: Add a per tracepoint counter attribute to get raw sample Frederic Weisbecker
-- strict thread matches above, loose matches on Subject: below --
2009-08-13 8:27 Frederic Weisbecker
2009-08-13 8:27 ` [PATCH 2/2] perf tools: Add a general option to enable raw sample records Frederic Weisbecker
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=20090814100721.GB5992@nowhere \
--to=fweisbec@gmail.com \
--cc=acme@redhat.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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