All of lore.kernel.org
 help / color / mirror / Atom feed
From: Prarit Bhargava <prarit@redhat.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Borislav Petkov <bp@alien8.de>,
	linux-kernel@vger.kernel.org, tigran@aivazian.fsnet.co.uk,
	x86@kernel.org, andi@firstfloor.org
Subject: Re: [PATCH] x86, microcode, Fix long microcode load time when firmware file is missing [v2]
Date: Mon, 28 Oct 2013 11:11:01 -0400	[thread overview]
Message-ID: <526E7E85.2000009@redhat.com> (raw)
In-Reply-To: <20131028150656.GA15440@khazad-dum.debian.net>



On 10/28/2013 11:06 AM, Henrique de Moraes Holschuh wrote:
> On Mon, 28 Oct 2013, Borislav Petkov wrote:
>> So Prarit, please split this patch into changes which *directly* address
>> the issue and other cleanups ontop. This will simplify review immensely
>> as having one single bulky patch is not easy on the eyes.
>>
>> Then, make sure to audit the lowlevel drivers whether they're already
>> issuing output on the error path before adding new printks arbitrarily.
> 
> Something else I couldn't check just from the description (and I apologise,
> but I did not look at your patch closely enough to check how you implemented
> the functionality on Intel): in the general case, it is NOT acceptable to
> bail out if you cannot find the firmware for the first processor.
> Mixed-stepping systems do exist, and you might need to update the microcode
> of, e.g, just the third processor.
> 
> AMD can get away with a half-done implementation of negative caching (or an
> "optimised one" depending on your PoV :) ) because they have per-family
> firmware files, so even mixed-stepping systems will require only the same
> file.  This is *not* true for Intel, which is really annoying.

Is that right? :(  I took Andi's comment to imply otherwise ...  If that's the
case then, yeah, back to the drawing board with this.

Andi (or anyone from Intel) -- care to offer a comment?

P.
> 

  reply	other threads:[~2013-10-28 15:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-28 12:06 [PATCH] x86, microcode, Fix long microcode load time when firmware file is missing [v2] Prarit Bhargava
2013-10-28 14:37 ` Borislav Petkov
2013-10-28 15:06   ` Henrique de Moraes Holschuh
2013-10-28 15:11     ` Prarit Bhargava [this message]
2013-10-28 15:23     ` Borislav Petkov
2013-10-28 15:05 ` Takashi Iwai
2013-10-28 15:12   ` Prarit Bhargava
2013-10-31 15:23   ` Prarit Bhargava

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=526E7E85.2000009@redhat.com \
    --to=prarit@redhat.com \
    --cc=andi@firstfloor.org \
    --cc=bp@alien8.de \
    --cc=hmh@hmh.eng.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tigran@aivazian.fsnet.co.uk \
    --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.