From: Adrian Bunk <bunk@fs.tum.de>
To: linux-kernel@vger.kernel.org
Subject: [0/4] [2.6 patch] better i386 CPU selection
Date: Sun, 14 Sep 2003 00:24:43 +0200 [thread overview]
Message-ID: <20030913222443.GN27368@fs.tum.de> (raw)
The patch is now splitted into the following four patches:
[1/4]
- changed the i386 CPU selection from a choice to single options for
every cpu
- renamed the M* variables to CPU_*, this is needed to ask the users
upgrading from older kernels instead of silently changing the
semantics
- X86_GOOD_APIC -> X86_BAD_APIC
- AMD Elan is a different subarch, you can't configure a kernel that
runs on both the AMD Elan and other i386 CPUs
- added optimizing CFLAGS for the AMD Elan
- gcc 2.95 supports -march=k6 (no need for check_gcc)
- help text changes/updates
[2/4]
move "struct movsl_mask movsl_mask" to usercopy.c
(CONFIG_X86_INTEL_USERCOPY is used on non-Intel CPUs)
[3/4]
- made arch/i386/kernel/cpu/Makefile CPU specific
[4/4]
- made arch/i386/kernel/cpu/mtrr/Makefile CPU specific
Dependencies between these patches:
- patch 3 requires 1+2
- patch 4 requires 1
The main part is patch 1.
Patch 2 fixes a small issue that only shows up with patch 3.
Patches 3+4 add some space optimizations by omitting unneeded code. They
are _not_ required, the main part is patch 1.
TODO:
- which CPUs exactly need X86_ALIGNMENT_16?
- change include/asm-i386/module.h to use some kind of bitmask
cu
Adrian
next reply other threads:[~2003-09-13 22:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-13 22:24 Adrian Bunk [this message]
2003-09-13 22:26 ` [1/4] [2.6 patch] better i386 CPU selection Adrian Bunk
2003-09-15 6:46 ` Michael Neuffer
2003-09-15 6:52 ` Adrian Bunk
2003-09-15 7:02 ` Michael Neuffer
2003-09-13 22:27 ` [2/4] " Adrian Bunk
2003-09-13 22:28 ` [3/4] " Adrian Bunk
2003-09-13 22:29 ` [4/4] " Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2003-09-25 18:02 [0/4] " Adrian Bunk
2003-09-26 22:38 ` Jan-Benedict Glaw
2003-09-26 22:47 ` Adrian Bunk
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=20030913222443.GN27368@fs.tum.de \
--to=bunk@fs.tum.de \
--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