[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1360592538-10643-1-git-send-email-bp@alien8.de>
Date: Mon, 11 Feb 2013 15:22:14 +0100
From: Borislav Petkov <bp@...en8.de>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: X86 ML <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org>,
Borislav Petkov <bp@...e.de>
Subject: [PATCH 0/4 -v3] x86, head_32: Some cleanups
From: Borislav Petkov <bp@...e.de>
Hi,
this is the new version with patch 5 from the old transformed into an
expanded, more verbose comment at the beginning of default_entry. No
changes otherwise.
Changelog:
v2:
Here's the next version with new_cpu_data left put and two minor fixlets
added at the end. The patchset was boot-tested on a bunch of baremetal
boxes and all QEMU cpu models - no issues.
Boot tests:
* baremetal:
- P4
- Atom n270
- 32-bit kernel on an AMD64 (F10h Phenom and Intel SNB)
* qemu, with cpu models:
- qemu64
- phenom
- core2duo
- kvm64
- qemu32
- kvm32
- coreduo
- 486{,SX}
- pentium{,2,3}
- athlon
- n270,+movbe
- Conroe
- Penryn
- Nehalem
- Westmere
- SandyBridge
- Haswell
- Opteron_G{1,2,3,4,5}
Why am I testing all those, you ask? Because I'm a sadistic mofo :-)
v1:
here are some initial low-hanging fruits wrt head_32.S cleanup. I've
made them as easily digestible as possible; after all, this is boot asm
and meddling with it tends to upset kernels.
Also, I've made the assumption that having boot_cpu_data.cpuid_level
contain the CPUID level for the boot cpu means that the APs have the
same CPUID level. This should be the case on X86.
They boot fine 486 and 486SX in qemu but I'd like to hear whether
the direction I'm going is ok before I continue testing them on real
hardware.
Borislav Petkov (4):
x86, head_32: Remove i386 pieces
x86: Detect CPUID support early at boot
x86, head_32: Remove second CPUID detection from default_entry
x86, head_32: Give the 6 label a real name
arch/x86/kernel/head_32.S | 93 ++++++++++++++++++-----------------------------
1 file changed, 36 insertions(+), 57 deletions(-)
--
1.8.1.3.535.ga923c31
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists