linux-kernel - Re: [RFC] perf: perf record sets inherit by default

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]

Date:	Tue, 11 May 2010 17:55:44 +0200
From:	Stephane Eranian <eranian@...gle.com>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Arnaldo Carvalho de Melo <acme@...radead.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Frédéric Weisbecker <fweisbec@...il.com>,
	mingo@...e.hu, Paul Mackerras <paulus@...ba.org>,
	"David S. Miller" <davem@...emloft.net>,
	perfmon2-devel@...ts.sf.net
Subject: Re: [RFC] perf: perf record sets inherit by default

On Tue, May 11, 2010 at 5:52 PM, Peter Zijlstra <peterz@...radead.org> wrote:
> On Tue, 2010-05-11 at 12:50 -0300, Arnaldo Carvalho de Melo wrote:
>
>> Nope, see above.
>
> Ah, -p/-t might make sense to default to inherit off indeed.
>
>
I would rather think that -p would inherit but not -t.
If I attach to a multi-threaded app with -p, I'd like all threads monitored.
But if I use -t to point to a specific thread within a process, then most
likely I care only about that thread.




-- 
Stephane Eranian  | EMEA Software Engineering
Google France | 38 avenue de l'Opéra | 75002 Paris
Tel : +33 (0) 1 42 68 53 00
This email may be confidential or privileged. If you received this
communication by mistake, please
don't forward it to anyone else, please erase all copies and
attachments, and please let me know that
it went to the wrong person. Thanks
--
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/