Bug 75022 - kernel build for ahtalon actually is done for i686
Summary: kernel build for ahtalon actually is done for i686
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel   
(Show other bugs)
Version: 8.0
Hardware: athlon Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2002-10-03 19:50 UTC by adler
Modified: 2007-04-18 16:47 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-12-17 01:00:27 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description adler 2002-10-03 19:50:40 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830

Description of problem:
Reading over the .spec file and associated patch files for the 2.4.18-14 kernel,
you build an i686 kernel when the target is athlon.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.get the kernel src.rpm file
2.install it
3.check spec and patch files

Additional info:

the patch file in question is: linux-2.4.18-smallpatches.patch. The
chuck in question is:

--- linux/arch/i386/Makefile~	Wed Aug  8 12:34:56 2001
+++ linux/arch/i386/Makefile	Wed Aug  8 17:40:17 2001
@@ -63,7 +63,7 @@
 ifdef CONFIG_MK7
-CFLAGS += $(shell if $(CC) -march=athlon -S -o /dev/null -xc /dev/null
>/dev/null 2>&1; then echo "-march=athlon"; else echo "-march=i686
-malign-functions=4"; fi) 
+CFLAGS += -march=i686 -malign-functions=4 
I've replaced the above code with

 ifdef CONFIG_MK7
-CFLAGS += $(shell if $(CC) -march=athlon -S -o /dev/null -xc /dev/null
>/dev/null 2>&1; then echo "-march=athlon"; else echo "-march=i686
-malign-functions=4"; fi) 
+CFLAGS += $(shell if $(CC) -march=athlon -S -o /dev/null -xc /dev/null
>/dev/null 2>&1; then echo "-march=athlon"; else echo "-march=i686
-falign-functions=4"; fi) 
and rebuilt the kernel rpms and installed them for the athlon target.
It seems to be running fine. I don't understand why you forced
the -march=i686 for athlons.

Comment 1 Arjan van de Ven 2002-10-03 19:55:06 UTC
we do this because -mathlon isn't actually tested a lot and has been buggy in
general :(

What the athlon kernel *does* bring are the fast memcpy/memset functions, which
are about 2x faster than the non-athlon ones.....

Comment 2 adler 2002-10-03 20:01:16 UTC
well, I do notice a general speed up of my desktop with this new kernel. Would
you like for me to report any anomolies? so far the system is doing fine.

Comment 3 Arjan van de Ven 2002-10-03 20:04:24 UTC
I'm absolutely interested in success/failure reports.
I might not be able to DO anything with it like dropping the patchlet soon
(right now I try to have a tree that compiles with both gcc 2.96 and 3.2, and I
*know* 2.96 -mathlon was bust), but in the future I will...

Comment 4 adler 2002-10-03 20:08:49 UTC
I will keep you guys posted.

Comment 5 adler 2002-10-03 21:27:44 UTC
do you guys want me to run a stress test on my recently built athlon system?

Comment 6 Arjan van de Ven 2002-10-03 21:30:45 UTC
I'm actually more worried about certain device drivers breaking. Stress tests
are good at finding broken algorithms in code, but miscompiles usually hit the
very first time code gets executed. And also device drivers tend to be more
sensitive to miscompiles due to, ehm, "sometimes questionable code quality".

Comment 7 adler 2002-10-03 22:38:19 UTC
hmmm... the only way to really test this is through a large user base. I suggest
that for the next beta release, you make sure the -march=athlon is set for the
athlon kernel build. Prety much all my devices have been tested with the athlon
built kernel I'm running... As I said, I'll keep you posted.

Note You need to log in before you can comment on or make changes to this bug.