All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mateusz Jończyk" <mat.jonczyk@o2.pl>
To: Thomas Gleixner <tglx@linutronix.de>, Willy Tarreau <w@1wt.eu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Testers wanted: Atom netbooks with x86_64 disabled by BIOS
Date: Sun, 28 Mar 2021 14:37:55 +0200	[thread overview]
Message-ID: <059b4775-e130-27c4-26fc-3a0eca07ddae@o2.pl> (raw)
In-Reply-To: <87lfa8cchf.ffs@nanos.tec.linutronix.de>

W dniu 28.03.2021 o 00:25, Willy Tarreau pisze:
> 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.

Thank you. It looks like your bootloader uses the 16-bit kernel boot protocol. 
The 16-bit kernel boot code checks for x86_64 presence with a similar message ( 
inside arch/x86/boot/cpu.c ), which I did not patch out. If you would like to 
test again, use the same patched kernel, but change in GRUB: "linux16" to 
"linux" and "initrd16" to "initrd" to use the 32-bit boot protocol. Which 
distribution and bootloader do you use?

W dniu 28.03.2021 o 03:07, Thomas Gleixner pisze:
 > 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.

Of course, force enabling x86_64 would require passing a kernel command line 
parameter with a prominent warning in documentation, just like with "forcepae".

Greetings,
Mateusz

  parent reply	other threads:[~2021-03-28 12:38 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
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 [this message]
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=059b4775-e130-27c4-26fc-3a0eca07ddae@o2.pl \
    --to=mat.jonczyk@o2.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --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 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.