From: Borislav Petkov <bp@alien8.de>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Fenghua Yu <fenghua.yu@intel.com>,
Steven Rostedt <rostedt@goodmis.org>,
H Peter Anvin <hpa@zytor.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
x86 <x86@kernel.org>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: x86-32: Early microcode loading stumbles over disabled DYNAMIC_FTRACE
Date: Fri, 23 Aug 2013 22:17:51 +0200 [thread overview]
Message-ID: <20130823201751.GA16046@pd.tnic> (raw)
In-Reply-To: <5217908E.2040702@siemens.com>
On Fri, Aug 23, 2013 at 06:40:46PM +0200, Jan Kiszka wrote:
> Below some hunks to get it working again - at least in the absence of
> any microcode in the initrd. Marking all involved functions as __init
> is another option (as __init implies notrace). But I bet there is more
> hidden. I see e.g. a pr_warn() in find_cpio_init that should trigger
> the issue as well if we hit the error it reports (btw. printing at
> this point of the boot should not work anyway, should it?).
I guess we can do early_printk there instead as x86_64_start_kernel()
does it but I'm not sure for the 32-bit case where we call
load_ucode_bsp/ap before we've even enabled paging.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-08-23 20:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 16:40 x86-32: Early microcode loading stumbles over disabled DYNAMIC_FTRACE Jan Kiszka
2013-08-23 20:17 ` Borislav Petkov [this message]
2013-08-26 8:50 ` Jan Kiszka
2013-08-30 15:36 ` H. Peter Anvin
2013-08-30 15:51 ` Steven Rostedt
2013-08-30 16:35 ` H. Peter Anvin
2013-08-30 17:03 ` Steven Rostedt
2013-08-30 17:16 ` H. Peter Anvin
2013-08-30 17:25 ` Steven Rostedt
2013-08-30 17:33 ` Jan Kiszka
2013-08-30 20:48 ` H. Peter Anvin
2013-08-31 0:17 ` Steven Rostedt
2013-08-31 5:07 ` Borislav Petkov
2013-08-31 5:23 ` Steven Rostedt
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=20130823201751.GA16046@pd.tnic \
--to=bp@alien8.de \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=jan.kiszka@siemens.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=x86@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