From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Borislav Petkov <bp@suse.de>
Cc: Ingo Molnar <mingo@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] x86/microcode: vsnprintf() might be unavailable
Date: Tue, 02 Jun 2015 19:49:53 +0300 [thread overview]
Message-ID: <1433263793.26331.42.camel@linux.intel.com> (raw)
In-Reply-To: <20150602162403.GD20576@pd.tnic>
On Tue, 2015-06-02 at 18:24 +0200, Borislav Petkov wrote:
> On Tue, Jun 02, 2015 at 05:56:43PM +0300, Andy Shevchenko wrote:
> > On Intel CPUs with x32 kernels we call load_builtin_intel_microcode() from
> > head_32.S on quite earlier stage. At that point sprintf() might be out of scope
> > to be called.
>
> Hrrm, I don't get that. How can sprintf() be out of scope?
Initial paging setup is involved? I just sent a small update to previous
patch. Please, look at it.
>
> Testing on 32-bit was successful here. How is x32 different?
Hmm… which Intel CPUs you run on?
Ah, one more thing we run our kernel from kexec (I hope it's not a case,
but who knows).
>
> Thanks.
>
--
Andy Shevchenko <andriy.shevchenko@intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2015-06-02 16:50 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 [this message]
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
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=1433263793.26331.42.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--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