From: Adrian Hunter <adrian.hunter@intel.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
linux-kernel@vger.kernel.org, David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Jiri Olsa <jolsa@redhat.com>, Mike Galbraith <efault@gmx.de>,
Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <peterz@infradead.org>,
Stephane Eranian <eranian@google.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH V9 04/14] perf tools: change machine__findnew_thread() to set thread pid
Date: Wed, 07 Aug 2013 11:34:23 +0300 [thread overview]
Message-ID: <5202068F.4000501@intel.com> (raw)
In-Reply-To: <87y58ex7k5.fsf@sejong.aot.lge.com>
On 07/08/13 10:51, Namhyung Kim wrote:
> On Mon, 5 Aug 2013 19:26:24 +0300, Adrian Hunter wrote:
>> Add a new parameter for 'pid' to machine__findnew_thread().
>> Change callers to pass 'pid' when it is known.
>>
> [SNIP]
>
>> @@ -198,7 +198,7 @@ static int perf_event__inject_buildid(struct perf_tool *tool,
>>
>> cpumode = event->header.misc & PERF_RECORD_MISC_CPUMODE_MASK;
>>
>> - thread = machine__findnew_thread(machine, event->ip.pid);
>> + thread = machine__findnew_thread(machine, event->ip.pid, event->ip.pid);
>
> Maybe I'm missing something. Why not use event->ip.tid here?
That is covered here:
http://marc.info/?l=linux-kernel&m=137513636309689&w=2
>
>
>> if (thread == NULL) {
>> pr_err("problem processing %d event, skipping it.\n",
>> event->header.type);
>> diff --git a/tools/perf/builtin-kmem.c b/tools/perf/builtin-kmem.c
>> index b49f5c5..c324778 100644
>> --- a/tools/perf/builtin-kmem.c
>> +++ b/tools/perf/builtin-kmem.c
>> @@ -305,7 +305,8 @@ static int process_sample_event(struct perf_tool *tool __maybe_unused,
>> struct perf_evsel *evsel,
>> struct machine *machine)
>> {
>> - struct thread *thread = machine__findnew_thread(machine, event->ip.pid);
>> + struct thread *thread = machine__findnew_thread(machine, event->ip.pid,
>> + event->ip.pid);
>
> And here.
>
> [SNIP]
>
>> diff --git a/tools/perf/builtin-script.c b/tools/perf/builtin-script.c
>> index 1cad370..a021e70 100644
>> --- a/tools/perf/builtin-script.c
>> +++ b/tools/perf/builtin-script.c
>> @@ -480,7 +480,8 @@ static int process_sample_event(struct perf_tool *tool __maybe_unused,
>> struct machine *machine)
>> {
>> struct addr_location al;
>> - struct thread *thread = machine__findnew_thread(machine, event->ip.tid);
>> + struct thread *thread = machine__findnew_thread(machine, event->ip.pid,
>> + event->ip.tid);
>
> But .tid used here.
>
>>
>> if (thread == NULL) {
>> pr_debug("problem processing %d event, skipping it.\n",
> [SNIP]
>> diff --git a/tools/perf/util/build-id.c b/tools/perf/util/build-id.c
>> index 5295625..0f9d27a 100644
>> --- a/tools/perf/util/build-id.c
>> +++ b/tools/perf/util/build-id.c
>> @@ -24,7 +24,8 @@ int build_id__mark_dso_hit(struct perf_tool *tool __maybe_unused,
>> {
>> struct addr_location al;
>> u8 cpumode = event->header.misc & PERF_RECORD_MISC_CPUMODE_MASK;
>> - struct thread *thread = machine__findnew_thread(machine, event->ip.pid);
>> + struct thread *thread = machine__findnew_thread(machine, event->ip.pid,
>> + event->ip.pid);
>
> Again, pid used.
>
>>
>> if (thread == NULL) {
>> pr_err("problem processing %d event, skipping it.\n",
>> @@ -47,7 +48,9 @@ static int perf_event__exit_del_thread(struct perf_tool *tool __maybe_unused,
>> __maybe_unused,
>> struct machine *machine)
>> {
>> - struct thread *thread = machine__findnew_thread(machine, event->fork.tid);
>> + struct thread *thread = machine__findnew_thread(machine,
>> + event->fork.pid,
>> + event->fork.tid);
>>
>> dump_printf("(%d:%d):(%d:%d)\n", event->fork.pid, event->fork.tid,
>> event->fork.ppid, event->fork.ptid);
>> diff --git a/tools/perf/util/event.c b/tools/perf/util/event.c
>> index 9541270..ec494a3 100644
>> --- a/tools/perf/util/event.c
>> +++ b/tools/perf/util/event.c
>> @@ -677,7 +677,8 @@ int perf_event__preprocess_sample(const union perf_event *event,
>> symbol_filter_t filter)
>> {
>> u8 cpumode = event->header.misc & PERF_RECORD_MISC_CPUMODE_MASK;
>> - struct thread *thread = machine__findnew_thread(machine, event->ip.pid);
>> + struct thread *thread = machine__findnew_thread(machine, event->ip.pid,
>> + event->ip.pid);
>
> And here.
>
>>
>> if (thread == NULL)
>> return -1;
>> diff --git a/tools/perf/util/machine.c b/tools/perf/util/machine.c
>> index 67ba572..16b84ac 100644
>> --- a/tools/perf/util/machine.c
>> +++ b/tools/perf/util/machine.c
>> @@ -30,7 +30,8 @@ int machine__init(struct machine *machine, const char *root_dir, pid_t pid)
>> return -ENOMEM;
>>
>> if (pid != HOST_KERNEL_ID) {
>> - struct thread *thread = machine__findnew_thread(machine, pid);
>> + struct thread *thread = machine__findnew_thread(machine, 0,
>> + pid);
>> char comm[64];
>>
>> if (thread == NULL)
>> @@ -282,9 +283,10 @@ static struct thread *__machine__findnew_thread(struct machine *machine,
>> return th;
>> }
>>
>> -struct thread *machine__findnew_thread(struct machine *machine, pid_t tid)
>> +struct thread *machine__findnew_thread(struct machine *machine, pid_t pid,
>> + pid_t tid)
>> {
>> - return __machine__findnew_thread(machine, 0, tid, true);
>> + return __machine__findnew_thread(machine, pid, tid, true);
>> }
>>
>> struct thread *machine__find_thread(struct machine *machine, pid_t tid)
>> @@ -294,7 +296,9 @@ struct thread *machine__find_thread(struct machine *machine, pid_t tid)
>>
>> int machine__process_comm_event(struct machine *machine, union perf_event *event)
>> {
>> - struct thread *thread = machine__findnew_thread(machine, event->comm.tid);
>> + struct thread *thread = machine__findnew_thread(machine,
>> + event->comm.pid,
>> + event->comm.tid);
>>
>> if (dump_trace)
>> perf_event__fprintf_comm(event, stdout);
>> @@ -975,7 +979,8 @@ int machine__process_mmap_event(struct machine *machine, union perf_event *event
>> return 0;
>> }
>>
>> - thread = machine__findnew_thread(machine, event->mmap.pid);
>> + thread = machine__findnew_thread(machine, event->mmap.pid,
>> + event->mmap.pid);
>
> Ditto.
>
> Hmm.. now I'm thinking that it's related to sharing map_groups between
> threads within a process. To do that, IMHO we need more sophisticated
> handling rather than passing either pid or tid depending on contexts?
Yes there is always more that could be done.
next prev parent reply other threads:[~2013-08-07 8:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 16:26 [PATCH V9 00/14] perf tools: some fixes and tweaks Adrian Hunter
2013-08-05 16:26 ` [PATCH V9 01/14] perf tools: add debug prints Adrian Hunter
2013-08-07 6:44 ` Namhyung Kim
2013-08-07 8:13 ` Adrian Hunter
2013-08-07 8:50 ` Namhyung Kim
2013-08-05 16:26 ` [PATCH V9 02/14] perf tools: allow non-matching sample types Adrian Hunter
2013-08-05 16:26 ` [PATCH V9 03/14] perf tools: add pid to struct thread Adrian Hunter
2013-08-05 16:26 ` [PATCH V9 04/14] perf tools: change machine__findnew_thread() to set thread pid Adrian Hunter
2013-08-07 7:51 ` Namhyung Kim
2013-08-07 8:34 ` Adrian Hunter [this message]
2013-08-07 8:40 ` Namhyung Kim
2013-08-05 16:26 ` [PATCH V9 05/14] perf tools: tidy up sample parsing overflow checking Adrian Hunter
2013-08-07 8:09 ` Namhyung Kim
2013-08-07 8:19 ` Adrian Hunter
2013-08-07 8:54 ` Namhyung Kim
2013-08-07 11:45 ` Adrian Hunter
2013-08-05 16:26 ` [PATCH V9 06/14] perf tools: remove unnecessary callchain validation Adrian Hunter
2013-08-05 16:26 ` [PATCH V9 07/14] perf tools: remove references to struct ip_event Adrian Hunter
2013-08-05 16:26 ` [PATCH V9 08/14] perf tools: move " Adrian Hunter
2013-08-07 8:22 ` Namhyung Kim
2013-08-05 16:26 ` [PATCH V9 09/14] perf: make events stream always parsable Adrian Hunter
2013-08-12 8:52 ` Peter Zijlstra
2013-08-05 16:26 ` [PATCH V9 10/14] perf tools: move perf_evlist__config() to a new source file Adrian Hunter
2013-08-05 16:26 ` [PATCH V9 11/14] perf tools: add support for PERF_SAMPLE_IDENTFIER Adrian Hunter
2013-08-05 16:26 ` [PATCH V9 12/14] perf tools: expand perf_event__synthesize_sample() Adrian Hunter
2013-08-05 16:26 ` [PATCH V9 13/14] perf tools: add a function to calculate sample event size Adrian Hunter
2013-08-05 16:26 ` [PATCH V9 14/14] perf tools: add a sample parsing test Adrian Hunter
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=5202068F.4000501@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@ghostprotocols.net \
--cc=dsahern@gmail.com \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
--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;
as well as URLs for NNTP newsgroup(s).