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: Wed, 18 Mar 2015 17:09:12 +0800	[thread overview]
Message-ID: <1426669752.20093.1@cpanel21.proisp.no> (raw)
In-Reply-To: <20150304114526.GE3516@pd.tnic>

On Wed, Mar 4, 2015 at 7:45 PM, Borislav Petkov <bp@alien8.de> wrote:
> On Wed, Mar 04, 2015 at 10:18:47AM +0100, Borislav Petkov wrote:
>>  Let me try to reproduce that here.
> 
> Well, it works fine on a single-socket box here:
> 
> [    1.045426] microcode: updated early to new patch_level=0x010000dc
> [    1.060957] microcode: CPU0: patch_level=0x010000dc
> [    1.061143] microcode: CPU1: patch_level=0x010000dc
> [    1.061310] microcode: CPU2: patch_level=0x010000dc
> [    1.061495] microcode: CPU3: patch_level=0x010000dc
> [    1.061677] microcode: CPU4: patch_level=0x010000dc
> [    1.061863] microcode: CPU5: patch_level=0x010000dc
> 
> That's early patching.
> 
> $ grep -E "(FIRMWARE|MICROCODE)" .config
> CONFIG_MICROCODE=y
> CONFIG_MICROCODE_INTEL=y
> CONFIG_MICROCODE_AMD=y
> CONFIG_MICROCODE_OLD_INTERFACE=y
> CONFIG_MICROCODE_INTEL_EARLY=y
> CONFIG_MICROCODE_AMD_EARLY=y
> CONFIG_MICROCODE_EARLY=y
> CONFIG_PREVENT_FIRMWARE_BUILD=y
> CONFIG_FIRMWARE_IN_KERNEL=y
> CONFIG_EXTRA_FIRMWARE="microcode_amd.bin microcode_amd_fam15h.bin 
> microcode_amd_fam16h.bin"
> CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware/amd-ucode"
> # CONFIG_DRM_LOAD_EDID_FIRMWARE is not set
> CONFIG_FIRMWARE_EDID=y
> CONFIG_FIRMWARE_MEMMAP=y
> # CONFIG_GOOGLE_FIRMWARE is not set
> # CONFIG_TEST_FIRMWARE is not set

Thanks for checking Boris!

I can't reproduce your early-loading case with this same config; I 
suspect your udev is loading the firmware which is available in the 
initramfs, or it's being loaded later from the rootfs non-early.

In my case, the microcode is in neither, hence we build it into the 
kernel image.

The full console log, config and bzImage are at 
https://resources.numascale.com/telemetry/

I find the changes I posted earlier fix this. Maybe I'm missing 
something still?

Daniel


  reply	other threads:[~2015-03-18  9:09 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 [this message]
2015-03-18 10:02           ` Borislav Petkov
2015-03-18 18:42             ` Borislav Petkov
2015-03-19  7:30               ` Daniel J Blueman
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=1426669752.20093.1@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