linux-kernel - Re: next-20081030: voyager compile busted

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <490A2C3D.4020202@zytor.com>
Date:	Thu, 30 Oct 2008 14:50:53 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	James Bottomley <James.Bottomley@...senPartnership.com>
CC:	Ingo Molnar <mingo@...e.hu>, Alexey Dobriyan <adobriyan@...il.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Thomas Gleixner <tglx@...utronix.de>,
	Yinghai Lu <yinghai@...nel.org>
Subject: Re: next-20081030: voyager compile busted

James Bottomley wrote:
> 
> Yes ... been having IRC conversations about that.  We'd need to use
> runtime patching to fix the performance regressions virtualisation has
> been causing us first ... but then we could use it for voyager.
> 

I thought we already were, at least to some degree (the call sites are
way too big and way bigger than they need to be, so we end up with a lot
of NOPs.  I proposed a solution to Jeremy at Kernel Summit, but he
basically said "I don't want to maintain that, I don't care about
hardware performance", which is understandable but highly unfortunate.)

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