[lkml]   [2017]   [May]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC] adding of TGID to ftrace output
On Thu, May 11, 2017 at 7:23 AM, Steven Rostedt <> wrote:
>> To fix the suggestion I made in the very beginning of this email, I
>> suggest a combination of trace_find_cmdline type of approach to save
>> the tgid of all current threads available, and then using
>> trace_sched_fork to find out what we missed (such as threads that were
>> added and removed.) I think this approach will be robust and not
>> affect any of the existing ftrace users (since we can make it a print
>> option). Thoughts?
>> Update: actually I find that someone already wrote an out-of-tree
>> patch for Android long time back during 3.10 kernel days that added a
>> 'print-tgid' option that saved tgid in the trace_save_cmdline function
>> and then find it later during output time:
>> It will be nice if we can have a more upstream ready version of this
>> patch or some other approach that you think works best. Thanks!
> Well, make that patch upstream friendly and post it to LMKL (Ccing me
> of course). And we'll talk about that.

Sure, will do. Thanks.


 \ /
  Last update: 2017-05-11 20:57    [W:0.045 / U:3.196 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site