From: Borislav Petkov <bp@alien8.de>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Problem with late AMD microcode reload/feedback
Date: Sun, 16 Dec 2018 11:06:45 +0100 [thread overview]
Message-ID: <20181216100645.GB815@zn.tnic> (raw)
In-Reply-To: <bac495ca-ccfd-3551-97ca-1444a391fa40@gmail.com>
On Sun, Dec 16, 2018 at 09:08:00AM +0100, Rafał Miłecki wrote:
> Thanks! I had no idea microcode_amd_fam17h.bin is a container with few
> microcodes. I thought there is a single microcode for a whole family
> (e.g. 17h).
It is a container for all F17h - you're simply making the wrong
assumption that it would have microcode for *all* F17h out there. Which
is not the case, because, well, there's not microcode for all of them
... yet.
:-)
IOW, there are only two patches released:
file offset: 60 (0x3c)
Patch 00: type 1, size: 3200 (0xc80)
ID: 0x08001227, CPU rev ID: 0x00008012
file offset: 3268 (0xcc4)
Patch 01: type 1, size: 3200 (0xc80)
ID: 0x0800820b, CPU rev ID: 0x00008082
> Using hex also makes more sense indeed!
> [ 44.127941] microcode: verify_and_add_patch: Added patch_id: 0x08001227, proc_id: 0x8012
> [ 44.127948] microcode: verify_and_add_patch: Added patch_id: 0x0800820b, proc_id: 0x8082
Yap.
> For my hack tests I'd like to replace my 0x0810100b with a 0x08101007.
Why would you even want to downgrade the microcode?!
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2018-12-16 10:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-15 23:46 Problem with late AMD microcode reload/feedback Rafał Miłecki
2018-12-16 0:05 ` Borislav Petkov
2018-12-16 8:08 ` Rafał Miłecki
2018-12-16 10:06 ` Borislav Petkov [this message]
2018-12-16 10:26 ` Rafał Miłecki
2018-12-16 10:44 ` Borislav Petkov
2018-12-16 11:02 ` Rafał Miłecki
2018-12-16 11:12 ` Borislav Petkov
2018-12-16 0:08 ` 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=20181216100645.GB815@zn.tnic \
--to=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=zajec5@gmail.com \
/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.