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 13:37:30 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, tglx@...utronix.de,
	peterz@...radead.org, tytso@....edu, arjan@...radead.org,
	srostedt@...hat.com
Subject: Re: [PATCH 4/4] trace: profile all if conditionals


* Steven Rostedt <rostedt@...dmis.org> wrote:

> 
> On Fri, 21 Nov 2008, Andrew Morton wrote:
> > >
> > > +#define if(cond) if (__builtin_constant_p((cond)) ? !!(cond) :		\
> > 
> > wheee...
> > 
> > Now how are you going to profile ?:, while, for(;expr;), etc? ;)

btw., there's hardware driven branch tracing and profiling in the 
works too, which captures all conditionals - including loops. Stay 
tuned :)

> I don't know. Give me a few months, I'll figure out a way ;-)

also loops generally have a more static (hence less interesting) 
prediction pattern - while for branches we frequently have a "should 
this branch be made likely/unlikely in the fastpath" question.

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