All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Ondrej Zary <linux@rainbow-software.org>
Cc: whiteheadm@acm.org, David Laight <David.Laight@aculab.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Alan Cox <gnomes@lxorguk.ukuu.org.uk>,
	David Woodhouse <dwmw2@infradead.org>,
	Guenter Roeck <linux@roeck-us.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Hugh Dickins <hughd@google.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Jiri Kosina <jikos@kernel.org>, Borislav Petkov <bp@alien8.de>,
	Kees Cook <keescook@chromium.org>,
	Jamie Iles <jamie@jamieiles.com>,
	Eduardo Valentin <eduval@amazon.com>,
	Laura Abbott <labbott@redhat.com>,
	Rik van Riel <riel@surriel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] x86 : i486 reporting to be vulnerable to Meltdown/Spectre_V1/Spectre_V2
Date: Tue, 13 Feb 2018 22:04:38 +0100	[thread overview]
Message-ID: <20180213210438.GA6569@amd> (raw)
In-Reply-To: <201802090941.41782.linux@rainbow-software.org>

[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]

Hi!

> > You might think this absolutely crazy, but I would be willing to test
> > such systems if I can get my hands on the needed hardware that I lack.
> > I am already doing sanity testing on Intel
> > i486/i586/i586-MMX/i686-PentiumPro systems, I just don't have the
> > clone cpus (Cyrix, etc).
> >
> > While few people are using the 32bit kernel, I don't think we want to
> > kill it completely just yet.
> 
> I have a working Cyrix MII (was actively using it last year, now upgraded to a 
> P3-based Celeron). Some AMD CPUs too - K6(maybe -2 or -3?), not sure about K5 
> and also a Rise mP6. But never got a WinChip.

I'm using Core Duo daily (backup machine, web browsing), and use
Pentium M as an ssh client say once in month.

> So the question is: what to test?

Self-compiling kernel is traditional stability test.

I do have two Geodes I believe, but the hardware is quite nasty to
use. (One has some kind of forth-based BIOS -- forgot the name).

> BTW. Kernel was not able to identify mP6 CPU 6 years ago, patches were 
> ignored.

You may want to re-send :-).
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2018-02-13 21:04 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-03  4:52 [BUG] x86 : i486 reporting to be vulnerable to Meltdown/Spectre_V1/Spectre_V2 tedheadster
2018-02-03  7:37 ` David Woodhouse
2018-02-06 18:33   ` tedheadster
2018-02-06 19:02     ` Greg Kroah-Hartman
2018-02-06 19:10       ` David Woodhouse
2018-02-06 19:13         ` Guenter Roeck
2018-02-06 19:17           ` David Woodhouse
2018-02-06 19:24             ` tedheadster
2018-02-06 20:45               ` tedheadster
2018-02-06 20:54                 ` David Woodhouse
2018-02-06 22:11                   ` tedheadster
2018-02-07  8:18                     ` Ondrej Zary
2018-02-08 13:49                       ` Alan Cox
2018-02-08 15:22                         ` Arnd Bergmann
2018-02-08 17:02                           ` David Laight
2018-02-08 17:27                             ` tedheadster
2018-02-08 21:50                               ` Arnd Bergmann
2018-02-09  8:41                               ` Ondrej Zary
2018-02-13 21:04                                 ` Pavel Machek [this message]
2018-02-15  9:53                                   ` What was last kernel that booted on hardware XY? database was Re: [BUG] x86 : i486 reporting to be vulnerable to Meltdown/Spectre_V1/Spectre_V2A Pavel Machek
2018-02-15 13:16                                     ` tedheadster
2018-02-17 21:16                                       ` Pavel Machek
2018-02-17 22:39                                         ` tedheadster
2018-02-23  8:07                                           ` Pavel Machek
2018-02-08 17:50                             ` [BUG] x86 : i486 reporting to be vulnerable to Meltdown/Spectre_V1/Spectre_V2 tedheadster
2018-02-08 20:52                               ` Alan Cox
2018-02-13 21:04                                 ` Pavel Machek
2018-02-13 23:45                                   ` Alan Cox
2018-02-08 21:16                           ` Alan Cox
2018-02-08 21:57                             ` Arnd Bergmann
2018-02-06 21:59                 ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180213210438.GA6569@amd \
    --to=pavel@ucw.cz \
    --cc=David.Laight@aculab.com \
    --cc=arnd@arndb.de \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=dwmw2@infradead.org \
    --cc=eduval@amazon.com \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=hughd@google.com \
    --cc=jamie@jamieiles.com \
    --cc=jikos@kernel.org \
    --cc=keescook@chromium.org \
    --cc=labbott@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rainbow-software.org \
    --cc=linux@roeck-us.net \
    --cc=riel@surriel.com \
    --cc=tglx@linutronix.de \
    --cc=whiteheadm@acm.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.