linux-kernel - Re: [PATCH 2/4] x86: remove unused code and data in nexgen.c

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:	Wed, 23 Apr 2008 19:19:52 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Dmitri Vorobiev <dmitri.vorobiev@...il.com>,
	Andi Kleen <andi@...stfloor.org>, mingo@...e.hu,
	tglx@...utronix.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/4] x86: remove unused code and data in nexgen.c

On Sun, 20 Apr 2008 15:34:53 -0400
"H. Peter Anvin" <hpa@...or.com> wrote:

> Dmitri Vorobiev wrote:
> >>
> >> Also NexGen was never shipped anyways, but bought by AMD and became
> >> the K6. So I assume whatever this file is supposed to do is done
> >> by amd.c anyways.
> > 
> > IOW, you claim that now it's safe enough to throw away the NexGen
> > altogether?
> > 
> 
> If it never shipped, then yes, it should be safe to remove.  We don't 
> support other vendors that never went to product, e.g. RISE or Montalvo.

There are/were a few Nexgen boxes out there - strange beast where the
BIOS code emulated some instructions. So few I doubt killing it off is a
problem at all.

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