public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Blueman <daniel@numascale.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Quentin Casasnovas <quentin.casasnovas@oracle.com>,
	Steffen Persvold <sp@numascale.com>,
	linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH] x86: Unbreak early processor microcode loading
Date: Thu, 19 Mar 2015 15:30:23 +0800	[thread overview]
Message-ID: <1426750223.3578.2@cpanel21.proisp.no> (raw)
In-Reply-To: <20150318184249.GC3249@pd.tnic>

On Thu, Mar 19, 2015 at 2:42 AM, Borislav Petkov <bp@alien8.de> wrote:
> On Wed, Mar 18, 2015 at 11:02:27AM +0100, Borislav Petkov wrote:
>>  I don't like the ifdeffery in your solution and would like to try 
>> to fix
>>  it in a cleaner way. Unless you come up with a better solution 
>> first.
> 
> Ok, how about this below? It is more involved but finds and loads the
> microcode built-in into the kernel in the early loader which is when
> you want to load microcode anyway. Only AMD for now but that should be
> enough for testing.
[]

Neat; I added the 'amd-ucode/' directory prefix to the string and 
adjusted the buffer size, and the microcode is loaded, but we see 
consistent hangs when onlining core 32 on the first server.

Further investigation shows the BIOS in this platform isn't loading the 
microcode after the Hypertransport reconfig warm-boot (though other 
platforms do), so it's a better solution I engage with the vendor to 
fix their BIOS, rather than working around it in the kernel at this 
time.

Many thanks!
  Daniel


  reply	other threads:[~2015-03-19  7:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03 15:10 [PATCH] x86: Unbreak early processor microcode loading Daniel J Blueman
2015-03-03 16:38 ` Borislav Petkov
2015-03-04  8:27   ` Daniel J Blueman
2015-03-04  9:18     ` Borislav Petkov
2015-03-04 11:45       ` Borislav Petkov
2015-03-18  9:09         ` Daniel J Blueman
2015-03-18 10:02           ` Borislav Petkov
2015-03-18 18:42             ` Borislav Petkov
2015-03-19  7:30               ` Daniel J Blueman [this message]
2015-03-19  9:27                 ` Borislav Petkov
2015-04-29 18:23                   ` Henrique de Moraes Holschuh
2015-04-29 18:43                     ` Borislav Petkov
2015-04-29 20:54                       ` Henrique de Moraes Holschuh
2015-04-29 21:45                         ` 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=1426750223.3578.2@cpanel21.proisp.no \
    --to=daniel@numascale.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=quentin.casasnovas@oracle.com \
    --cc=sp@numascale.com \
    --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