From: Boris Ostrovsky <boris.ostrovsky@amd.com>
To: Gene Heskett <gheskett@wdtv.com>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>, <hpa@zytor.com>,
<mingo@elte.hu>, <tglx@linutronix.de>,
<herrmann.der.user@googlemail.com>, <bp@alien8.de>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86, microcode, AMD: Add support for family 16h processors
Date: Thu, 15 Nov 2012 18:35:17 -0500 [thread overview]
Message-ID: <50A57C35.10906@amd.com> (raw)
In-Reply-To: <201211151801.23160.gheskett@wdtv.com>
On 11/15/2012 06:01 PM, Gene Heskett wrote:
> On Thursday 15 November 2012, Henrique de Moraes Holschuh wrote:
>> On Thu, 15 Nov 2012, Boris Ostrovsky wrote:
>>> Add valid patch size for family 16h processors
>>>
>>> Signed-off-by: Boris Ostrovsky <boris.ostrovsky@amd.com>
>>
>> Is this something that needs to go to -stable ?
>
> IMO, and if I had an oar in this water, yes. Its been missing since the
> Intel folks started playing with it a couple years back up the log. I
> have the amd_ucode files in my /lib/firmware tree,
>
> root@coyote:/opt/os9# ls -l /lib/firmware/amd-ucode/
> total 76
> -rw-r--r-- 1 root root 642 2012-01-17 11:50 INSTALL
> -rw-r--r-- 1 root root 9987 2012-01-17 11:50 LICENSE
> -rw-r--r-- 1 root root 12404 2012-01-17 11:50 microcode_amd.bin
> -rw-r--r-- 1 root root 1526 2012-01-17 11:50 microcode_amd.bin.README
> -rw-r--r-- 1 root root 2644 2012-01-17 11:50 microcode_amd_fam15h.bin
> -rw-r--r-- 1 root root 510 2012-01-17 11:50
> microcode_amd_fam15h.bin.README
> -rw-r--r-- 1 root root 2012 2009-01-20 04:48 microcode_amd.phenom-V83
> -rw-r--r-- 1 root root 15020 2012-01-17 11:50 microcode_amd_solaris.bin
> -rw-r--r-- 1 root root 1685 2012-01-17 11:50
> microcode_amd_solaris.bin.README
> -rw-r--r-- 1 root root 6227 2012-01-17 11:50 README
>
> but I can't recall the last time I saw the code sign in during dmesg.
> Old, slow 4 core phenom here. AMD was forgotten about when the loading
> of it was moved from the kernel options to /etc/init.d/microcode. For
> an AMD user, that was not a show stopper, but it wasn't a Good Thing(TM)
> either.
One possibility is that BIOS already incorporated all patches (which
typically is the case) and so the driver doesn't have to do anything.
-boris
>
>>
>>> #define F1XH_MPB_MAX_SIZE 2048
>>> #define F14H_MPB_MAX_SIZE 1824
>>> #define F15H_MPB_MAX_SIZE 4096
>>>
>>> +#define F16H_MPB_MAX_SIZE 3458
>>>
>>> switch (c->x86) {
>>>
>>> case 0x14:
>>> @@ -198,6 +199,9 @@ static unsigned int verify_patch_size(int cpu, u32
>>> patch_size,
>>>
>>> case 0x15:
>>> max_size = F15H_MPB_MAX_SIZE;
>>> break;
>>>
>>> + case 0x16:
>>> + max_size = F16H_MPB_MAX_SIZE;
>>> + break;
>>>
>>> default:
>>> max_size = F1XH_MPB_MAX_SIZE;
>>> break;
>>
>> Because it looks like without this patch, some valid microcode updates
>> would be rejected by the kernel...
>
>
> Cheers, Gene
>
next prev parent reply other threads:[~2012-11-15 23:35 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 [this message]
2012-11-17 14:41 ` Borislav Petkov
2012-11-17 15:29 ` Henrique de Moraes Holschuh
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=50A57C35.10906@amd.com \
--to=boris.ostrovsky@amd.com \
--cc=bp@alien8.de \
--cc=gheskett@wdtv.com \
--cc=herrmann.der.user@googlemail.com \
--cc=hmh@hmh.eng.br \
--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
Powered by JetHome