linux-kernel - Re: [PATCH] [58/58] x86: remove support for the Rise CPU

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]

Message-ID: <469F7BB9.1000202@garzik.org>
Date:	Thu, 19 Jul 2007 10:56:57 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Andi Kleen <ak@...e.de>
CC:	Alan Cox <alan@...rguk.ukuu.org.uk>, Adrian Bunk <bunk@...sta.de>,
	patches@...-64.org, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] [58/58] x86: remove support for the Rise CPU

Andi Kleen wrote:
> On Thursday 19 July 2007 13:13:40 Alan Cox wrote:
>>> - It's not only code, it also bloats everyone's kernel image.
>> Its a miniscule piece of code that is discarded on boot. Yes it might
>> make the image 100 bytes longer, but have you priced a 160GB disk
>> recently. I don't think 100 bytes of disk and 0 of memory really is worth
>> saving for any risk at all. Its not even worth the time to apply the
>> patch.
> 
> The patch is already applied.

Er, huh?  It's not upstream.


> Besides the CPU will likely boot even without special handling.

You don't know this.  Why risk it?  Just leave the CPU magic as-is.

	Jeff


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