All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
Cc: Joerg Roedel <jroedel@suse.de>, Meelis Roos <mroos@linux.ee>,
	Thomas Gleixner <tglx@linutronix.de>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org, Andrea Arcangeli <aarcange@redhat.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Not-so-old machines without PAE was Re: 32-bit PTI with THP = userspace corruption
Date: Tue, 23 Oct 2018 11:11:27 +0200	[thread overview]
Message-ID: <20181023091127.GA9843@amd> (raw)
In-Reply-To: <20181022194817.148796e6@alans-desktop>

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

On Mon 2018-10-22 19:48:17, Alan Cox wrote:
> On Mon, 22 Oct 2018 09:56:42 +0200
> Joerg Roedel <jroedel@suse.de> wrote:
> 
> > On Sun, Oct 21, 2018 at 02:37:45PM +0200, Pavel Machek wrote:
> > > On Tue 2018-09-18 14:00:30, Alan Cox wrote:  
> > > > There are pretty much no machines that don't support PAE and are still
> > > > even vaguely able to boot a modern Linux kernel. The oddity is the
> > > > Pentium-M but most distros shipped a hack to use PAE on the Pentium M
> > > > anyway as it seems to work fine.  
> > > 
> > > I do have some AMD Geode here, in form of subnotebook. Definitely
> > > newer then Pentium Ms, but no PAE...  
> > 
> > Are the AMD Geode chips affected by Meltdown?
> 
> Geode for AMD was just a marketing name.
> 
> The AMD athlon labelled as 'Geode' will behave like any other Athlon but
> I've not seen anyone successfully implement Meltdown on the Athlon so it's
> probably ok. 
> 
> The earlier NatSemi ones are not AFAIK vulnerable to either. The later
> ones might do Spectre (they have branch prediction which is disabled on
> the earlier ones) but quite possibly not enough to be attacked usefully -
> and you can turn it off anyway if you care.
> 
> And I doubt your subnotebook can usefully run modern Linux since the
> memory limit on most Geode was about 64MB.

Well, let me see. The machine is not too useful because of dead
battery, but I don't believe RAM would be a problem. It has 512MB or
more, IIRC. Missing PAE is, and missing instructions are. And horrible
keyboard and bad driver support from Linux. And... Ouch and fact that
I use its power supply to power something else.

It looks similar to this:
https://hexus.net/tech/news/laptop/13994-kohjinsha-launches-impressive-subnotebook-twist/
(but has no touchscreen).

Bios is "built 03/02/2007".

CPU is "AuthenticAMD" family 5 model 10, "Geode(TM) Integrated Processor
by AMD PCS". 500 MHz, flags "fpu de pse tsc msr cx8 sep pge cmov
clflush mmx mmxext 3dnowext 3dnow". 512MB RAM.

This is not a suitable compile server, but still could work as a
subnotebook given right software...


									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-10-23  9:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-30 18:09 32-bit PTI with THP = userspace corruption Meelis Roos
2018-08-30 20:55 ` Joerg Roedel
2018-08-31  4:12   ` Meelis Roos
2018-08-31  7:07     ` Joerg Roedel
2018-09-08 10:24       ` Thomas Gleixner
2018-09-11 11:49         ` Joerg Roedel
2018-09-11 11:58           ` Meelis Roos
2018-09-11 12:12             ` Joerg Roedel
2018-09-18 13:00               ` Alan Cox
2018-10-21 12:37                 ` Pavel Machek
2018-10-22  7:56                   ` Joerg Roedel
2018-10-22 18:48                     ` Alan Cox
2018-10-23  9:11                       ` Pavel Machek [this message]
2018-10-22 20:56                     ` Pavel Machek
2018-09-11 18:20           ` Linus Torvalds
2018-08-31  7:10   ` Meelis Roos

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=20181023091127.GA9843@amd \
    --to=pavel@ucw.cz \
    --cc=aarcange@redhat.com \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=jroedel@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mroos@linux.ee \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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.