linux-kernel - Re: [PATCH 4/4] trace: profile all if conditionals

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:	Sun, 23 Nov 2008 21:51:22 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Andi Kleen <andi@...stfloor.org>,
	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	Theodore Tso <tytso@....edu>,
	Arjan van de Ven <arjan@...radead.org>,
	Steven Rostedt <srostedt@...hat.com>
Subject: Re: [PATCH 4/4] trace: profile all if conditionals

> My work evolves around not adding any userspace tool that is not already
> supported by busybox. I'm not against anyone else doing this work. It's 

That seems very limiting and arbitary, like tieing your hands behind your back.
Why is it ok to add code to the kernel and ok not adding code
to userland?

> This all sounds great, and perhaps someone might decide to do this. The 
> full branch tracer I added, I did in a few hours and tested on both x86 
> and PPC. That was because I was waiting on output from a test running on 
> another box that was taking a couple of hours, and I got bored.
> 
> I'm not against any of the suggestions you make. I'm just waiting for 
> someone else to do it ;-)

I just suggested the perfctr method for completeness. It actually
doesn't need much work, you can probably quite easily do it 
with the existing oprofile infrastructure to get the data,
although the output is not very nice with opreport.

But gcov is already done and existing for some time. And for
most usages unless you require minimal runtime overhead it is 
likely the better option. We also used it successfully for some 
testing here. It also has hit l-k some time ago. I don't know the 
latest merge status, but I think it hit -mm at least at some point.

-Andi

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