From: Borislav Petkov <bp@alien8.de>
To: Matt Fleming <matt.fleming@intel.com>
Cc: Trevor Turner <turn3r.tr3v0r@gmail.com>,
Randy Dunlap <rdunlap@xenotime.net>,
linux-kernel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: K7/Athlon Optimization Causes Build Fail on Kernel 3.3 i686
Date: Thu, 29 Mar 2012 12:48:23 +0200 [thread overview]
Message-ID: <20120329104822.GA17233@x1.osrc.amd.com> (raw)
In-Reply-To: <1333008855.4289.3.camel@mfleming-mobl1.ger.corp.intel.com>
On Thu, Mar 29, 2012 at 09:14:15AM +0100, Matt Fleming wrote:
> Hmm... I think what might make more sense is to make EFI (not EFI_STUB)
> depend on !MK7, since I doubt people actually need both MK7 and any EFI
> firmware support.
... and EFI_STUB depends on EFI, yeah, true story.
Here's an updated patch, Trevor pls try this one instead, thanks.
--
>From b3419ea2f2d38e758022bab17855eb9df8ee43c0 Mon Sep 17 00:00:00 2001
From: Borislav Petkov <bp@alien8.de>
Date: Thu, 29 Mar 2012 09:39:51 +0200
Subject: [PATCH] AMD, K7: Fix compilation error when EFI is enabled
Trevor Turner reported that building the 3.3 kernel on his K7 box fails.
Reproducing the issue locally got us also the exact build error:
arch/x86/boot/compressed/eboot.o: In function `efi_main':
eboot.c:(.text+0x1530): undefined reference to `_mmx_memcpy'
eboot.c:(.text+0x17d0): undefined reference to `_mmx_memcpy'
make[2]: *** [arch/x86/boot/compressed/vmlinux] Error 1
make[1]: *** [arch/x86/boot/compressed/vmlinux] Error 2
make[1]: *** Waiting for unfinished jobs....
due to the fact that K7 has special MMX memcpy routines which EFI uses
through memcpy but is not linked against them thus the build failure.
Instead of making this work, we decided to make EFI and K7 mutually
exclusive since they're from different epochs anyway. The patch below
fixes that.
Reported-by: Trevor Turner <turn3r.tr3v0r@gmail.com>
Cc: Matt Fleming <matt.fleming@intel.com>
Signed-off-by: Borislav Petkov <bp@alien8.de>
---
arch/x86/Kconfig | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 5bed94e189fa..95d2b7c9b74a 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -1502,7 +1502,7 @@ config ARCH_RANDOM
config EFI
bool "EFI runtime service support"
- depends on ACPI
+ depends on ACPI && !MK7
---help---
This enables the kernel to use EFI runtime services that are
available (such as the EFI variable services).
--
1.7.9
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2012-03-29 10:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 13:56 K7/Athlon Optimization Causes Build Fail on Kernel 3.3 i686 Trevor Turner
2012-03-27 17:29 ` Randy Dunlap
2012-03-28 0:03 ` Trevor Turner
2012-03-28 11:19 ` Borislav Petkov
2012-03-28 16:33 ` Trevor Turner
2012-03-28 17:10 ` Borislav Petkov
2012-03-28 17:13 ` Randy Dunlap
2012-03-28 17:27 ` Borislav Petkov
2012-03-29 7:48 ` Borislav Petkov
2012-03-29 8:14 ` Matt Fleming
2012-03-29 10:48 ` Borislav Petkov [this message]
2012-03-29 18:21 ` Trevor Turner
2012-03-29 18:28 ` H. Peter Anvin
2012-03-29 20:46 ` Borislav Petkov
2012-03-29 20:49 ` H. Peter Anvin
2012-03-30 7:47 ` Borislav Petkov
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=20120329104822.GA17233@x1.osrc.amd.com \
--to=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=rdunlap@xenotime.net \
--cc=turn3r.tr3v0r@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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