[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 12 Dec 2013 15:56:26 +0200
From: Adrian Hunter <adrian.hunter@...el.com>
To: David Ahern <dsahern@...il.com>
CC: Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
Frederic Weisbecker <fweisbec@...il.com>,
Jiri Olsa <jolsa@...hat.com>, Mike Galbraith <efault@....de>,
Namhyung Kim <namhyung@...il.com>,
Paul Mackerras <paulus@...ba.org>,
Stephane Eranian <eranian@...gle.com>,
Andi Kleen <ak@...ux.intel.com>
Subject: Re: [PATCH v0 13/71] perf tools: Add machine__get_thread_pid()
On 11/12/13 21:28, David Ahern wrote:
> On 12/11/13, 5:36 AM, Alexander Shishkin wrote:
>> From: Adrian Hunter <adrian.hunter@...el.com>
>>
>> Add a function to get the pid from the tid.
>>
>> This is needed when using the sched_switch
>> tracepoint to follow object code execution.
>> sched_switch identifies the thread but, to
>> find the process mmaps, we need the process
>> pid.
>
> Are you looking up the current or next task? If the former why not use
> sample->pid rather than parsing the sched_switch tracepoint?
Next pid unfortunately.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists