linux-kernel - Re: [PATCH 1/3] ftrace: add function tracing to single thread

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.1.10.0811251914400.26424@gandalf.stny.rr.com>
Date:	Tue, 25 Nov 2008 19:16:47 -0500 (EST)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Frédéric Weisbecker <fweisbec@...il.com>
cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Steven Rostedt <srostedt@...hat.com>
Subject: Re: [PATCH 1/3] ftrace: add function tracing to single thread


On Wed, 26 Nov 2008, Fr?d?ric Weisbecker wrote:

> 2008/11/25 Steven Rostedt <rostedt@...dmis.org>:
> > From: Steven Rostedt <srostedt@...hat.com>
> >
> > Impact: feature to function trace a single thread
> >
> > This patch adds the ability to function trace a single thread.
> > The file:
> >
> >  /debugfs/tracing/set_ftrace_pid
> 
> 
> That's a good idea!
> 
> About the pid, I think they are unique (which is not the case for tgid
> for multiple threads).
> pid are tgid + number of the thread....
> 
> But perhaps I'm wrong....

Hmm, I can see that there could be times we would want to trace all 
threads, and times to trace only a single thread. This should default to 
the tgid.

We could echo in "t:pid" to trace per thread. and just "pid" to trace non 
all threads in a group.

-- Steve

--
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/