public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Harald Hoyer <harald@redhat.com>
Cc: Josh Boyer <jwboyer@fedoraproject.org>,
	Laura Abbott <labbott@redhat.com>, X86 ML <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/6] x86/microcode: Merge early loader
Date: Mon, 9 Nov 2015 11:11:59 +0100	[thread overview]
Message-ID: <20151109101159.GA14962@pd.tnic> (raw)
In-Reply-To: <56406A75.3030006@redhat.com>

On Mon, Nov 09, 2015 at 10:42:13AM +0100, Harald Hoyer wrote:
> Will this work with kernels not supporting the microcode loading?
> Theoretically the old kernels would just unpack all cpios one after
> the other, right?

Well, what we should be doing is adding two paths to the initrd:

for AMD:	kernel/x86/microcode/AuthenticAMD.bin
for Intel:	kernel/x86/microcode/GenuineIntel.bin

I.e., the microcode blobs become part of the initrd, see
Documentation/x86/early-microcode.txt. The loader goes and opens the one
it needs at boot time.

You could also add a switch for convenience, something like
--no-microcode or so, so that dracut doesn't add it but if one wants to
not add microcode, one could also move it away from, say, /lib/firmware/
so that dracut simply doesn't find it. The --no-microcode might be more
convenient though.

Kernels which don't support microcode loading would simply not look for
that path.

Let me know if this doesn't make sense and if I need to test/look at
patches.

Thanks.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.

  reply	other threads:[~2015-11-09 10:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20  9:54 [PATCH 0/6] x86/microcode: Merge the early loader Borislav Petkov
2015-10-20  9:54 ` [PATCH 1/6] x86/microcode: Unmodularize driver Borislav Petkov
2015-10-21 10:07   ` [tip:ras/core] x86/microcode: Unmodularize the microcode driver tip-bot for Borislav Petkov
2015-10-20  9:54 ` [PATCH 2/6] x86/microcode: Merge early loader Borislav Petkov
2015-10-21 10:07   ` [tip:ras/core] x86/microcode: Merge the early microcode loader tip-bot for Borislav Petkov
2015-11-06 19:22   ` [PATCH 2/6] x86/microcode: Merge early loader Josh Boyer
2015-11-06 19:31     ` Borislav Petkov
2015-11-09  9:42       ` Harald Hoyer
2015-11-09 10:11         ` Borislav Petkov [this message]
2015-10-20  9:54 ` [PATCH 3/6] x86/microcode: Remove modularization leftovers Borislav Petkov
2015-10-21 10:08   ` [tip:ras/core] " tip-bot for Borislav Petkov
2015-10-20  9:54 ` [PATCH 4/6] x86/microcode/amd: Remove maintainers from comments Borislav Petkov
2015-10-21 10:08   ` [tip:ras/core] " tip-bot for Borislav Petkov
2015-10-20  9:54 ` [PATCH 5/6] x86/microcode/intel: Move ifdef DEBUG inside the function Borislav Petkov
2015-10-21 10:08   ` [tip:ras/core] x86/microcode/intel: Move #ifdef " tip-bot for Borislav Petkov
2015-10-20  9:54 ` [PATCH 6/6] MAINTAINERS: Unify microcode driver section Borislav Petkov
2015-10-21 10:09   ` [tip:ras/core] MAINTAINERS: Unify the " tip-bot for 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=20151109101159.GA14962@pd.tnic \
    --to=bp@alien8.de \
    --cc=harald@redhat.com \
    --cc=jwboyer@fedoraproject.org \
    --cc=labbott@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --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