From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Borislav Petkov <bp@alien8.de>, Gene Heskett <gheskett@wdtv.com>,
Boris Ostrovsky <boris.ostrovsky@amd.com>,
hpa@zytor.com, mingo@elte.hu, tglx@linutronix.de,
herrmann.der.user@googlemail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86, microcode, AMD: Add support for family 16h processors
Date: Sat, 17 Nov 2012 13:29:19 -0200 [thread overview]
Message-ID: <20121117152918.GA16697@khazad-dum.debian.net> (raw)
In-Reply-To: <20121117144117.GD16441@x1.osrc.amd.com>
On Sat, 17 Nov 2012, Borislav Petkov wrote:
> On Thu, Nov 15, 2012 at 06:35:17PM -0500, Boris Ostrovsky wrote:
> > One possibility is that BIOS already incorporated all patches (which
> > typically is the case) and so the driver doesn't have to do anything.
>
> /proc/cpuinfo contains ucode version and the processor's f/m/s, which
> is enough information to tell us whether your old phenom needs ucode
> patching.
Maybe, however F/M/S information is incomplete, not to mention trying to
rebuild the proper processor signature from it is anything but
forward-proof. For Intel, it is also useless, you also need the processor
flags...
If /proc/cpuinfo is to be useful for microcode purposes, it should add a
microcode signature line, with CPUID(1).EAX, and on Intel processors, also a
second parameter with the processor flags mask (I don't know if AMD needs
something else other than CPUID(1).EAX).
--
"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
next prev parent reply other threads:[~2012-11-17 15:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 18:41 Boris Ostrovsky
2012-11-15 20:24 ` Andreas Herrmann
2012-11-15 20:45 ` Henrique de Moraes Holschuh
2012-11-15 21:26 ` Boris Ostrovsky
2012-11-15 21:48 ` H. Peter Anvin
2012-11-15 21:49 ` Henrique de Moraes Holschuh
2012-11-15 21:55 ` Andreas Herrmann
2012-11-15 23:01 ` Gene Heskett
2012-11-15 23:35 ` Boris Ostrovsky
2012-11-17 14:41 ` Borislav Petkov
2012-11-17 15:29 ` Henrique de Moraes Holschuh [this message]
2012-11-17 15:31 ` Borislav Petkov
2012-11-17 18:34 ` Gene Heskett
2012-11-17 19:41 ` H. Peter Anvin
2012-11-17 20:07 ` Gene Heskett
2012-11-17 20:42 ` H. Peter Anvin
2012-11-17 19:54 ` Andreas Herrmann
2012-11-17 20:11 ` Gene Heskett
2012-11-19 14:23 ` Borislav Petkov
2012-11-15 21:55 ` [tip:x86/urgent] " tip-bot for Boris Ostrovsky
2012-11-21 7:36 ` tip-bot for Boris Ostrovsky
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=20121117152918.GA16697@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=boris.ostrovsky@amd.com \
--cc=bp@alien8.de \
--cc=gheskett@wdtv.com \
--cc=herrmann.der.user@googlemail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®