linux-kernel - Re: i686 quirk for AMD Geode

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:  <20091112210351.459994c2@mycelium.queued.net>
Date:	Thu, 12 Nov 2009 21:03:51 -0500
From:	Andres Salomon <dilinger@...labora.co.uk>
To:	linux-kernel@...r.kernel.org
Subject:  Re: i686 quirk for AMD Geode

On Thu, 12 Nov 2009 13:18:05 +0100
Pavel Machek <pavel@....cz> wrote:

> Hi!
> 
> > > > The Geode NX (which no one has mentioned yet) is an Athlon
> > > > derived chip.
> > > 
> > > *As far as I know* K6 didn't have NOPL, whereas K7 does.
> > 
> > Which would be mroe indication that the Geode LX may in fact be a K6
> > based CPU design.  The Geode NX is very clearly an Athlon (K7) and
> > AMD has never even tried to hide that.  They have never said what
> > the LX is based on, other than it isn't based on the GX
> > (fortunately, that thing was a buggy piece of crap).
> 
> Interesting...geode gx being buggy? I know pentium was famous for the
> fdiv bug, but never heard of geode gx problems...

http://www.amd.com/files/connectivitysolutions/geode/geode_gx/31533E_gx_2.1_specupdate.pdf

1.4 is my favorite.  The branch prediction logic can send the
instruction pointer off to la-la land.

While at olpc, we had a sad discussion about what the *real* impact of
the workaround was...




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