From: "Mateusz Jończyk" <mat.jonczyk@o2.pl>
To: linux-kernel@vger.kernel.org
Cc: "Mateusz Jończyk" <mat.jonczyk@o2.pl>
Subject: Re: Testers wanted: Atom netbooks with x86_64 disabled by BIOS
Date: Sat, 27 Mar 2021 22:13:22 +0100 [thread overview]
Message-ID: <20210327211322.121708-1-mat.jonczyk@o2.pl> (raw)
In-Reply-To: <20210327203218.119372-1-mat.jonczyk@o2.pl>
W dniu 27.03.2021 o 21:32, Mateusz Jończyk pisze:
> Hello,
>
> There are some netbooks with Intel Atom processors that have 64-bit
> support disabled by BIOS. Theoretically, the processor supports 64-bit
> operation, but BIOS allows only 32-bit code to run.
>
> I wonder whether the 64-bit mode is really disabled in the CPU or only
> hidden in the CPUID flags. If the latter, the computer could be made to
> run a 64-bit kernel.
>
> Similarly, there are some Pentium M processors that support PAE
> (Physical Address Extensions), but do not show this in CPUID. They could
> be made to run distributions that require PAE with the "forcepae" kernel
> command line parameter.
>
> I would like to ask people with such netbooks to try to run a 64-bit kernel
> with this patch applied.
>
> When a patched 64-bit kernel is run in `qemu-system-i386`, the virtual
> machine restarts instantly. Without this patch in such a case a 64-bit
> kernel hangs indefinitely (inside .Lno_longmode in head_64.S).
I have made two mistakes:
- I left commented out code,
- I have commented out lines with '#'. The code compiled though.
Attaching corrected patch, please excuse me.
Greetings,
Mateusz
Signed-off-by: Mateusz Jończyk <mat.jonczyk@o2.pl>
---
arch/x86/boot/compressed/head_64.S | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/x86/boot/compressed/head_64.S b/arch/x86/boot/compressed/head_64.S
index e94874f4bbc1..a9f0415da7c2 100644
--- a/arch/x86/boot/compressed/head_64.S
+++ b/arch/x86/boot/compressed/head_64.S
@@ -111,8 +111,6 @@ SYM_FUNC_START(startup_32)
leal rva(boot_stack_end)(%ebp), %esp
call verify_cpu
- testl %eax, %eax
- jnz .Lno_longmode
/*
* Compute the delta between where we were compiled to run at
--
2.25.1
next prev parent reply other threads:[~2021-03-27 21:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-27 20:32 Mateusz Jończyk
2021-03-27 21:13 ` Mateusz Jończyk [this message]
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
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=20210327211322.121708-1-mat.jonczyk@o2.pl \
--to=mat.jonczyk@o2.pl \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®