From: "H. Peter Anvin" <hpa@zytor.com>
To: Dmitry Adamushko <dmitry.adamushko@gmail.com>
Cc: Peter Oruba <peter.oruba@amd.com>,
Tigran Aivazian <tigran@aivazian.fsnet.co.uk>,
Max Krasnyansky <maxk@qualcomm.com>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [patch 0/4] x86: AMD microcode patch loading v2 fixes
Date: Fri, 01 Aug 2008 08:26:19 -0700 [thread overview]
Message-ID: <48932B1B.70303@zytor.com> (raw)
In-Reply-To: <b647ffbd0808010425r16db2957i3e7212903a698c19@mail.gmail.com>
Dmitry Adamushko wrote:
> Tigran, Peter,
>
> may a firmware package contain a few 'microcode' updates for a specific cpu?
>
> And if so, does each of them provide independent 'errata' fixes? [*]
>
> (or they are just different versions of the same self-consistent/full
> 'microcode' update and we may need to apply each of them just e.g.
> because we can't jump from stepping X.1 to X.3 without applying X.2 in
> between?
>
> if it's [1], then I wonder why only a single 'microcode' update (which
> has been previously cached in 'uci->mc') is being applied for the case
> of system-wide resume (apply_microcode_check_cpu()). Don't we need to
> go through the full cpu_request_microcode() cycle to consider all
> updates?
>
No, there is only ever one microcode; you only run the latest one.
-hpa
next prev parent reply other threads:[~2008-08-01 15:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 15:41 [patch 0/4] x86: AMD microcode patch loading v2 fixes Peter Oruba
2008-07-29 15:41 ` [patch 1/4] x86: AMD microcode patch loader style corrections Peter Oruba
2008-07-29 15:41 ` [patch 2/4] x86: Intel " Peter Oruba
2008-07-29 15:41 ` [patch 3/4] x86: Moved function declarations out from AMD microcode patch loader to heade file Peter Oruba
2008-07-29 15:41 ` [patch 4/4] x86: Minor pointer type cast in AMD microcode patch loader Peter Oruba
2008-07-29 16:18 ` [patch 0/4] x86: AMD microcode patch loading v2 fixes Dmitry Adamushko
2008-07-29 17:49 ` Max Krasnyansky
2008-07-29 19:37 ` Dmitry Adamushko
2008-07-30 9:28 ` Peter Oruba
2008-07-30 9:57 ` Dmitry Adamushko
2008-07-30 10:34 ` Dmitry Adamushko
2008-07-30 16:35 ` Max Krasnyansky
2008-07-30 18:38 ` Dmitry Adamushko
2008-07-31 21:24 ` Ingo Molnar
2008-08-01 2:23 ` Max Krasnyansky
2008-07-30 16:54 ` Max Krasnyansky
2008-07-30 20:59 ` Dmitry Adamushko
2008-08-01 2:18 ` Max Krasnyansky
2008-08-01 11:25 ` Dmitry Adamushko
2008-08-01 12:21 ` Peter Oruba
2008-08-01 15:26 ` H. Peter Anvin [this message]
2008-07-31 21:27 ` Ingo Molnar
2008-07-31 22:02 ` Dmitry Adamushko
2008-07-31 22:12 ` Ingo Molnar
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=48932B1B.70303@zytor.com \
--to=hpa@zytor.com \
--cc=dmitry.adamushko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
--cc=mingo@elte.hu \
--cc=peter.oruba@amd.com \
--cc=tglx@linutronix.de \
--cc=tigran@aivazian.fsnet.co.uk \
/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