All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
	Andi Kleen <andi@firstfloor.org>,
	jolsa@kernel.org, namhyung@kernel.org,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH v4 03/15] perf tools script: Filter COMM/FORK/.. events by CPU
Date: Fri, 8 Mar 2019 10:39:01 -0300	[thread overview]
Message-ID: <20190308133901.GB26260@kernel.org> (raw)
In-Reply-To: <20190307110231.GB8979@krava>

Em Thu, Mar 07, 2019 at 12:02:31PM +0100, Jiri Olsa escreveu:
> On Wed, Mar 06, 2019 at 04:23:40PM +0200, Adrian Hunter wrote:
> > On 5/03/19 4:47 PM, Andi Kleen wrote:
> > > From: Andi Kleen <ak@linux.intel.com>
> > > 
> > > The --cpu option only filtered samples. Filter other perf events,
> > > such as COMM, FORK, SWITCH by the CPU too.
> > 
> > Because tasks can migrate from cpu to cpu, we probably need to process most
> > of the events anyway, even if they are not printed.
> 
> agreed, I wonder we could just make the perf_event__fprintf conditional

Humm, probably just do the filtering on PERF_RECORD_SAMPLE is enough?
I.e. having the other PERF_RECORD_{COMM,MMAP,} etc is required in face
of migration.

- Arnaldo
 
> jirka
> 
> > 
> > > 
> > > Reported-by: Jiri Olsa <jolsa@kernel.org>
> > > Signed-off-by: Andi Kleen <ak@linux.intel.com>
> > > ---
> > >  tools/perf/builtin-script.c | 24 ++++++++++++++++++++++++
> > >  1 file changed, 24 insertions(+)
> > > 
> > > diff --git a/tools/perf/builtin-script.c b/tools/perf/builtin-script.c
> > > index fbc440bdf880..3813f60d1dc0 100644
> > > --- a/tools/perf/builtin-script.c
> > > +++ b/tools/perf/builtin-script.c
> > > @@ -2038,6 +2038,9 @@ static int process_comm_event(struct perf_tool *tool,
> > >  	struct perf_evsel *evsel = perf_evlist__id2evsel(session->evlist, sample->id);
> > >  	int ret = -1;
> > >  
> > > +	if (cpu_list && !test_bit(sample->cpu, cpu_bitmap))
> > > +		return 0;
> > > +
> > >  	thread = machine__findnew_thread(machine, event->comm.pid, event->comm.tid);
> > >  	if (thread == NULL) {
> > >  		pr_debug("problem processing COMM event, skipping it.\n");
> > > @@ -2073,6 +2076,9 @@ static int process_namespaces_event(struct perf_tool *tool,
> > >  	struct perf_evsel *evsel = perf_evlist__id2evsel(session->evlist, sample->id);
> > >  	int ret = -1;
> > >  
> > > +	if (cpu_list && !test_bit(sample->cpu, cpu_bitmap))
> > > +		return 0;
> > > +
> > >  	thread = machine__findnew_thread(machine, event->namespaces.pid,
> > >  					 event->namespaces.tid);
> > >  	if (thread == NULL) {
> > > @@ -2108,6 +2114,9 @@ static int process_fork_event(struct perf_tool *tool,
> > >  	struct perf_session *session = script->session;
> > >  	struct perf_evsel *evsel = perf_evlist__id2evsel(session->evlist, sample->id);
> > >  
> > > +	if (cpu_list && !test_bit(sample->cpu, cpu_bitmap))
> > > +		return 0;
> > > +
> > >  	if (perf_event__process_fork(tool, event, sample, machine) < 0)
> > >  		return -1;
> > >  
> > > @@ -2141,6 +2150,9 @@ static int process_exit_event(struct perf_tool *tool,
> > >  	struct perf_session *session = script->session;
> > >  	struct perf_evsel *evsel = perf_evlist__id2evsel(session->evlist, sample->id);
> > >  
> > > +	if (cpu_list && !test_bit(sample->cpu, cpu_bitmap))
> > > +		return 0;
> > > +
> > >  	thread = machine__findnew_thread(machine, event->fork.pid, event->fork.tid);
> > >  	if (thread == NULL) {
> > >  		pr_debug("problem processing EXIT event, skipping it.\n");
> > > @@ -2174,6 +2186,9 @@ static int process_mmap_event(struct perf_tool *tool,
> > >  	struct perf_session *session = script->session;
> > >  	struct perf_evsel *evsel = perf_evlist__id2evsel(session->evlist, sample->id);
> > >  
> > > +	if (cpu_list && !test_bit(sample->cpu, cpu_bitmap))
> > > +		return 0;
> > > +
> > >  	if (perf_event__process_mmap(tool, event, sample, machine) < 0)
> > >  		return -1;
> > >  
> > > @@ -2206,6 +2221,9 @@ static int process_mmap2_event(struct perf_tool *tool,
> > >  	struct perf_session *session = script->session;
> > >  	struct perf_evsel *evsel = perf_evlist__id2evsel(session->evlist, sample->id);
> > >  
> > > +	if (cpu_list && !test_bit(sample->cpu, cpu_bitmap))
> > > +		return 0;
> > > +
> > >  	if (perf_event__process_mmap2(tool, event, sample, machine) < 0)
> > >  		return -1;
> > >  
> > > @@ -2238,6 +2256,9 @@ static int process_switch_event(struct perf_tool *tool,
> > >  	struct perf_session *session = script->session;
> > >  	struct perf_evsel *evsel = perf_evlist__id2evsel(session->evlist, sample->id);
> > >  
> > > +	if (cpu_list && !test_bit(sample->cpu, cpu_bitmap))
> > > +		return 0;
> > > +
> > >  	if (perf_event__process_switch(tool, event, sample, machine) < 0)
> > >  		return -1;
> > >  
> > > @@ -2266,6 +2287,9 @@ process_lost_event(struct perf_tool *tool,
> > >  	struct perf_evsel *evsel = perf_evlist__id2evsel(session->evlist, sample->id);
> > >  	struct thread *thread;
> > >  
> > > +	if (cpu_list && !test_bit(sample->cpu, cpu_bitmap))
> > > +		return 0;
> > > +
> > >  	thread = machine__findnew_thread(machine, sample->pid,
> > >  					 sample->tid);
> > >  	if (thread == NULL)
> > > 
> > 

-- 

- Arnaldo

  reply	other threads:[~2019-03-08 13:39 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-05 14:47 Support sample context in perf report Andi Kleen
2019-03-05 14:47 ` [PATCH v4 01/15] perf tools: Add utility function to fetch executable Andi Kleen
2019-03-06 20:53   ` Arnaldo Carvalho de Melo
2019-03-06 21:08     ` Andi Kleen
2019-03-09 19:59   ` [tip:perf/urgent] perf thread: Generalize function to copy from thread addr space from intel-bts code tip-bot for Andi Kleen
2019-03-05 14:47 ` [PATCH v4 02/15] perf tools script: Support insn output for normal samples Andi Kleen
2019-03-08 13:37   ` Arnaldo Carvalho de Melo
2019-03-22 21:59   ` [tip:perf/urgent] perf " tip-bot for Andi Kleen
2019-03-05 14:47 ` [PATCH v4 03/15] perf tools script: Filter COMM/FORK/.. events by CPU Andi Kleen
2019-03-06 14:23   ` Adrian Hunter
2019-03-07 11:02     ` Jiri Olsa
2019-03-08 13:39       ` Arnaldo Carvalho de Melo [this message]
2019-03-08 15:08         ` Andi Kleen
2019-03-05 14:47 ` [PATCH v4 04/15] perf tools report: Support nano seconds Andi Kleen
2019-03-22 21:59   ` [tip:perf/urgent] perf report: Support output in nanoseconds tip-bot for Andi Kleen
2019-03-05 14:47 ` [PATCH v4 05/15] perf tools report: Parse time quantum Andi Kleen
2019-03-08 13:45   ` Arnaldo Carvalho de Melo
2019-03-08 13:52     ` Arnaldo Carvalho de Melo
2019-03-08 17:39       ` Andi Kleen
2019-03-22 22:01   ` [tip:perf/urgent] perf " tip-bot for Andi Kleen
2019-03-05 14:47 ` [PATCH v4 06/15] perf tools report: Support time sort key Andi Kleen
2019-03-05 14:47 ` [PATCH v4 07/15] perf tools report: Use less for scripts output Andi Kleen
2019-03-08 13:47   ` Arnaldo Carvalho de Melo
2019-03-09  7:52     ` Feng Tang
2019-03-05 14:47 ` [PATCH v4 08/15] perf tools report: Support running scripts for current time range Andi Kleen
2019-03-05 14:47 ` [PATCH v4 09/15] perf tools report: Support builtin perf script in scripts menu Andi Kleen
2019-03-05 14:47 ` [PATCH v4 10/15] perf tools: Add utility function to print ns time stamps Andi Kleen
2019-03-08 13:51   ` Arnaldo Carvalho de Melo
2019-03-22 22:00   ` [tip:perf/urgent] perf time-utils: Add utility function to print time stamps in nanoseconds tip-bot for Andi Kleen
2019-03-05 14:47 ` [PATCH v4 11/15] perf tools report: Implement browsing of individual samples Andi Kleen
2019-03-05 14:47 ` [PATCH v4 12/15] perf tools: Add some new tips describing the new options Andi Kleen
2019-03-05 14:47 ` [PATCH v4 13/15] perf tools report: Add custom scripts to script menu Andi Kleen
2019-03-05 14:47 ` [PATCH v4 14/15] perf tools script: Add array bound checking to list_scripts Andi Kleen
2019-03-05 14:47 ` [PATCH v4 15/15] perf tools ui: Fix ui popup browser for many entries Andi Kleen
2019-03-07 10:57 ` Support sample context in perf report Jiri Olsa
2019-03-07 16:57   ` Andi Kleen

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=20190308133901.GB26260@kernel.org \
    --to=arnaldo.melo@gmail.com \
    --cc=adrian.hunter@intel.com \
    --cc=ak@linux.intel.com \
    --cc=andi@firstfloor.org \
    --cc=jolsa@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=namhyung@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.