All of lore.kernel.org
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Borislav Petkov <bp@amd64.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	"Yu, Fenghua" <fenghua.yu@intel.com>, X86-ML <x86@kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>,
	Andreas Herrmann <andreas.herrmann3@amd.com>
Subject: Re: [PATCH 2/2] x86, microcode: Make reload interface per system
Date: Wed, 20 Jun 2012 20:59:18 -0300	[thread overview]
Message-ID: <20120620235918.GF4223@khazad-dum.debian.net> (raw)
In-Reply-To: <20120620234611.GA3440@aftab.osrc.amd.com>

On Thu, 21 Jun 2012, Borislav Petkov wrote:
> * we don't need the userspace tool to split the blob - we have one
> single file we load and the driver picks out what it needs.

Yes.  A smarter userspace tool is useful to reduce the size of the
microcode blob that ends up linked to the kernel or added to the
initramfs in distros that generate the initramfs at the target system
when you install a kernel (like Debian does), but it is in no way
*required*.

Typically you go from ~512KiB uncompressed (all binary microcodes) to
8-32KiB uncompressed when you target only the [online] processors of the
current system.  Nice for embedded, I suppose.

> In the end, we have one unified ucode loading procedure:
> 
> 1. put the blob in /lib/firmware/...
> 2. echo 1 > /sys/devices/system/cpu/microcode/reload
> 
> That's it - it can't be simpler than that.

Indeed.  And with an invariant microcode name for the Intel driver, one
can use the standard userspace tooling that detects which firmware needs
to go into the initramfs when no special tooling is installed.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

  parent reply	other threads:[~2012-06-20 23:59 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-19 16:03 [PATCH 0/2] x86, microcode: Reload ucode only per-system Borislav Petkov
2012-06-19 16:03 ` [PATCH 1/2] x86, microcode: Sanitize per-cpu microcode reloading interface Borislav Petkov
2012-06-19 18:25   ` Henrique de Moraes Holschuh
     [not found]   ` <CANDHA0iu+QtQn=UxjpN34U=Ob4ABkZc4VWpPT5EidAgZm59JJQ@mail.gmail.com>
2012-06-19 23:15     ` Yu, Fenghua
2012-06-19 23:38       ` Borislav Petkov
2012-06-19 16:03 ` [PATCH 2/2] x86, microcode: Make reload interface per system Borislav Petkov
2012-06-19 18:26   ` Henrique de Moraes Holschuh
     [not found]   ` <CANDHA0jf2fLOtg1E6CbyNM=omn=kj=YoRJ3VTkNA0AhkS-MLtg@mail.gmail.com>
2012-06-19 23:10     ` Yu, Fenghua
2012-06-19 23:28       ` Borislav Petkov
2012-06-20  3:26         ` Henrique de Moraes Holschuh
2012-06-20  9:57           ` Borislav Petkov
2012-06-20 23:10             ` Henrique de Moraes Holschuh
2012-06-20  8:59         ` Peter Zijlstra
2012-06-20  9:56           ` Borislav Petkov
2012-06-20 10:08             ` Peter Zijlstra
2012-06-20 10:19               ` Borislav Petkov
2012-06-20 10:22                 ` Peter Zijlstra
2012-06-20 10:27                   ` Borislav Petkov
2012-06-20 10:33                     ` Peter Zijlstra
2012-06-20 11:09                       ` Borislav Petkov
2012-06-22 18:57                         ` H. Peter Anvin
2012-06-23  1:54                           ` Henrique de Moraes Holschuh
2012-06-23  2:26                             ` H. Peter Anvin
2012-06-20 23:21                   ` Henrique de Moraes Holschuh
2012-06-20 23:26                     ` Borislav Petkov
2012-06-22 16:26                 ` Nix
2012-06-22 18:21                   ` H. Peter Anvin
2012-06-23  1:32                     ` Henrique de Moraes Holschuh
2012-06-20 23:08           ` Henrique de Moraes Holschuh
2012-06-20 23:10             ` H. Peter Anvin
2012-06-20 23:23               ` Borislav Petkov
2012-06-20 23:27                 ` H. Peter Anvin
2012-06-20 23:32                   ` Borislav Petkov
2012-06-20 23:34                     ` H. Peter Anvin
2012-06-20 23:46                       ` Borislav Petkov
2012-06-20 23:48                         ` H. Peter Anvin
2012-06-21 10:07                           ` Borislav Petkov
2012-06-21 23:27                             ` H. Peter Anvin
2012-06-22  2:56                               ` Borislav Petkov
2012-06-22  3:19                                 ` H. Peter Anvin
2012-06-22  3:36                                   ` Borislav Petkov
2012-06-22  6:41                                     ` Markus Trippelsdorf
2012-06-20 23:59                         ` Henrique de Moraes Holschuh [this message]
2012-06-20 23:50                     ` Henrique de Moraes Holschuh
2012-06-21  0:02                       ` Henrique de Moraes Holschuh
2012-06-21  8:24             ` Peter Zijlstra
2012-06-21  9:58               ` Borislav Petkov
2012-06-21 23:28                 ` H. Peter Anvin
2012-06-21 23:00               ` Henrique de Moraes Holschuh
2012-06-22  3:01                 ` Borislav Petkov
2012-06-20 13:18         ` 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=20120620235918.GF4223@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=andreas.herrmann3@amd.com \
    --cc=bp@amd64.org \
    --cc=fenghua.yu@intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.