From: Borislav Petkov <bp@suse.de>
To: "Shevchenko, Andriy" <andriy.shevchenko@intel.com>
Cc: "andy.shevchenko@gmail.com" <andy.shevchenko@gmail.com>,
"mingo@kernel.org" <mingo@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mika.westerberg@linux.intel.com"
<mika.westerberg@linux.intel.com>
Subject: Re: [PATCH 1/1] x86/microcode: vsnprintf() might be unavailable
Date: Wed, 3 Jun 2015 23:13:52 +0200 [thread overview]
Message-ID: <20150603211352.GC4706@pd.tnic> (raw)
In-Reply-To: <1433353745.26331.58.camel@intel.com>
On Wed, Jun 03, 2015 at 05:49:05PM +0000, Shevchenko, Andriy wrote:
> On Wed, 2015-06-03 at 18:27 +0300, Andy Shevchenko wrote:
> > > > I have a totally empty screen (serial console). So, if you teach me
> > > > how to gather that I could do it later on.
> > >
> > > That'll be hard - you'd probably need a hardware debugger or something
> > > special to get a RIP or other data that early... Or hack up some very
> > > early console printing with BIOS methods and so on. hpa had something
> > > like that somewhere AFAIR...
> >
> > I could try kvm / qemu as well, though there might be not the same
> > conditions.
>
> Yeah, qemu runs fine.
So, I did some more experiments and even if we build the string
properly, we choke later in get_builtin_firmware(). Actually, we don't
choke but we don't find firwmare because we're running with physical
addresses and those __start/__stop_builtin_fw things are virtual
addresses. Yuck!
So I'm gravitating towards disabling builtin microcode loading on
32-bit. For now, as the merge window is going to be open soon, until
we/I have fixed it properly. And I don't have a clear solution now - all
I can think of is ugly ifdeffery which I'd like to avoid.
Grrr.
---
diff --git a/arch/x86/kernel/cpu/microcode/amd_early.c b/arch/x86/kernel/cpu/microcode/amd_early.c
index 9208a36d0f03..9243cd839829 100644
--- a/arch/x86/kernel/cpu/microcode/amd_early.c
+++ b/arch/x86/kernel/cpu/microcode/amd_early.c
@@ -230,6 +230,7 @@ static void apply_ucode_in_initrd(void *ucode, size_t size, bool save_patch)
static bool __init load_builtin_amd_microcode(struct cpio_data *cp, int family)
{
+#ifdef CONFIG_X86_64
char fw_name[36] = "amd-ucode/microcode_amd.bin";
if (family >= 0x15)
@@ -237,6 +238,9 @@ static bool __init load_builtin_amd_microcode(struct cpio_data *cp, int family)
"amd-ucode/microcode_amd_fam%.2xh.bin", family);
return get_builtin_firmware(cp, fw_name);
+#else
+ return false;
+#endif
}
void __init load_ucode_amd_bsp(int family)
diff --git a/arch/x86/kernel/cpu/microcode/intel_early.c b/arch/x86/kernel/cpu/microcode/intel_early.c
index 10dff3f3f686..b4858d892592 100644
--- a/arch/x86/kernel/cpu/microcode/intel_early.c
+++ b/arch/x86/kernel/cpu/microcode/intel_early.c
@@ -523,6 +523,7 @@ EXPORT_SYMBOL_GPL(save_mc_for_early);
static bool __init load_builtin_intel_microcode(struct cpio_data *cp)
{
+#ifdef CONFIG_X86_64
u32 eax = 0x00000001, ebx, ecx = 0, edx;
int family, model, stepping;
char name[30];
@@ -536,6 +537,9 @@ static bool __init load_builtin_intel_microcode(struct cpio_data *cp)
sprintf(name, "intel-ucode/%02x-%02x-%02x", family, model, stepping);
return get_builtin_firmware(cp, name);
+#else
+ return false;
+#endif
}
static __initdata char ucode_name[] = "kernel/x86/microcode/GenuineIntel.bin";
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2015-06-03 21:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 14:56 Andy Shevchenko
2015-06-02 16:24 ` Borislav Petkov
2015-06-02 16:49 ` Andy Shevchenko
2015-06-02 17:00 ` Borislav Petkov
2015-06-02 17:31 ` Andy Shevchenko
2015-06-03 10:56 ` Borislav Petkov
2015-06-03 15:27 ` Andy Shevchenko
2015-06-03 17:49 ` Shevchenko, Andriy
2015-06-03 21:13 ` Borislav Petkov [this message]
2015-06-04 9:21 ` [PATCH] x86/microcode: Disable builtin microcode loading on 32-bit for now Borislav Petkov
2015-06-04 9:47 ` Shevchenko, Andriy
2015-06-02 16:46 ` [PATCH 1/1] x86/microcode: vsnprintf() might be unavailable Andy Shevchenko
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=20150603211352.GC4706@pd.tnic \
--to=bp@suse.de \
--cc=andriy.shevchenko@intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=mingo@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
Powered by JetHome