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 12:59:46 -0300
From:	Arnaldo Carvalho de Melo <acme@...radead.org>
To:	Stephane Eranian <eranian@...gle.com>
Cc:	Peter Zijlstra <peterz@...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

Em Tue, May 11, 2010 at 05:55:44PM +0200, Stephane Eranian escreveu:
> 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.

Ok, so fine tuning of the inherit flag is needed, i.e. we need both a
--inherit and a --no-inherit, well, good thing is that I think that the
option parsing stuff we, erm, inherited from git does just that, lemme
check how it works in this case more precisely...

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