Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Message-ID: <059b4775-e130-27c4-26fc-3a0eca07ddae@o2.pl>
Date:   Sun, 28 Mar 2021 14:37:55 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:87.0) Gecko/20100101
 Thunderbird/87.0
Content-Language: en-GB
To:     Thomas Gleixner <tglx@linutronix.de>, Willy Tarreau <w@1wt.eu>
Cc:     linux-kernel@vger.kernel.org
References: <20210327203218.119372-1-mat.jonczyk@o2.pl>
 <20210327211322.121708-1-mat.jonczyk@o2.pl> <20210327232551.GA20783@1wt.eu>
 <87lfa8cchf.ffs@nanos.tec.linutronix.de>
From:   =?UTF-8?Q?Mateusz_Jo=c5=84czyk?= <mat.jonczyk@o2.pl>
Subject: Re: Testers wanted: Atom netbooks with x86_64 disabled by BIOS
In-Reply-To: <87lfa8cchf.ffs@nanos.tec.linutronix.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Precedence: bulk

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