linux-kernel - Re: [PATCH] Scheduler Profiling

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] [day] [month] [year] [list]

Message-ID: <20070912143223.GB2287@one.firstfloor.org>
Date:	Wed, 12 Sep 2007 16:32:23 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
Cc:	Andi Kleen <andi@...stfloor.org>, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org, "H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH] Scheduler Profiling - Use Immediate Values

> The idea is not to hide the unlikely, but to leave the opportunity to
> make this primitive evolve in something that won't depend on a load
> immediate and only require patching of a jump, given the appropriate gcc
> support (yet to come).

If that ever happens the code can be still changed. But i don't think
it's a good idea to uglify the code for something that if it 
ever exists will be a long time away.

Besides if gcc supports it I assume the gcc support could 
also be written in a way that makes it possible to hide it inside
a standard if ()

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