public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Willy Tarreau <w@1wt.eu>, Mateusz Jonczyk <mat.jonczyk@o2.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Testers wanted: Atom netbooks with x86_64 disabled by BIOS
Date: Sun, 28 Mar 2021 03:07:24 +0200	[thread overview]
Message-ID: <87lfa8cchf.ffs@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20210327232551.GA20783@1wt.eu>

On Sun, Mar 28 2021 at 00:25, Willy Tarreau wrote:
> On Sat, Mar 27, 2021 at 10:13:22PM +0100, Mateusz Jonczyk wrote:
> FWIW I tested on my ASUS 1025C which runs on an Atom N2600 forced to
> 32-bit. I had already tried in the past but wanted to give it a try
> again in case I'd have missed anything. Sadly it didn't work, I'm
> still getting the "requires an x86-64 CPU" message.
>
> Given these machines were really cheap, I've always suspected that they
> employ cheaper, low-grade CPUs, possibly having been subject to reduced
> tests where x86_64-specific parts were not even verified and might be
> defective. This may explain why they forcefully disable long mode there,
> but that's just speculation.

There are some of these '32bit only' CPUs out there in the wild which
actually support long mode. Some of them even do not have the long mode
CPUID bit fused out. But whether it works is a different story:

  - If the CPUID bit is on, then the chance is high, but it runs out of
    spec (guarantee wise)

  - If it's off is still might work by some definition of work as they
    might have fused off more or there are actual defects in some 64bit
    only area which are irrelevant when in 32bit mode.

Even if it could work perfectly fine, the BIOS/SMM/ucode can prevent
switching to long mode.

It's a lost cause.

Thanks,

        tglx

  reply	other threads:[~2021-03-28  1:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-27 20:32 Testers wanted: Atom netbooks with x86_64 disabled by BIOS Mateusz Jończyk
2021-03-27 21:13 ` Mateusz Jończyk
2021-03-27 23:25   ` Willy Tarreau
2021-03-28  1:07     ` Thomas Gleixner [this message]
2021-03-28  6:18       ` Willy Tarreau
     [not found]         ` <CAHp75Ve_Yhs3ib5yk=d-+bhb4vHpx-j6D4jGGBKuD2k1qv38Vg@mail.gmail.com>
2021-03-28 21:58           ` Willy Tarreau
2021-03-28 22:18             ` Thomas Gleixner
2021-03-29 10:59             ` Andy Shevchenko
2021-03-28 12:37       ` Mateusz Jończyk
2021-03-28 13:30         ` Willy Tarreau
2021-03-28 15:55           ` Willy Tarreau

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=87lfa8cchf.ffs@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mat.jonczyk@o2.pl \
    --cc=w@1wt.eu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox