public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Corbin <corbinbird@charter.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] AMD microcode updates - where are they?!
Date: Tue, 16 Jul 2019 22:21:07 -0500	[thread overview]
Message-ID: <fda97826-df7f-fdd8-65d7-2a8d1bf7bf5d@charter.net> (raw)
In-Reply-To: <21714265.1ZXtKVbesA@localhost>


On 7/14/19 8:26 AM, Mick wrote:
> Then I came across this old message regarding Piledriver CPUs:
> https://lists.debian.org/debian-security/2016/03/msg00084.html The
> post refers to model 2 of cpu family 21. Not all models in the same
> family, only model 2. So I am thinking although patch files are named
> per CPU family, whether they are applicable and applied as an update
> to the CPU is probably determined by the particular CPU *model*.
> Logically, errata in previous CPU revisions may have been fixed in
> later models of the same family and therefore such microcode updates
> would not be needed. When offered by the OS the CPU won't select to
> have them applied. This explains why my AMD models, which are later
> revisions of the same 15h family do not apply any microcode updates -
> they don't need them. Please share if you know differently and thank
> you all for your responses. 
Remember a while back when I mentioned that "lwp" had disappeared from
my /proc/cpuinfo?
They restored "lwp" with this commit :
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=7518922bd5b98b137af7aaf3c836f5a498e91609
So it stands to reason that the microcode only applies specific patches
to specific problems per CPU.


Reference :
> Darkstar ~ # cat /proc/cpuinfo
> processor    : 0
> vendor_id    : AuthenticAMD
> cpu family    : 21
> model        : 2
> model name    : AMD FX(tm)-9590 Eight-Core Processor
> stepping    : 0
> microcode    : 0x6000852
> cpu MHz        : 4685.390
> cache size    : 2048 KB
Output of /sys/devices/system/cpu/vulnerabilities :
>
> Darkstar ~ # cat /sys/devices/system/cpu/vulnerabilities/l1tf
> Not affected
> Darkstar ~ # cat /sys/devices/system/cpu/vulnerabilities/mds
> Not affected
> Darkstar ~ # cat /sys/devices/system/cpu/vulnerabilities/meltdown
> Not affected
> Darkstar ~ # cat
> /sys/devices/system/cpu/vulnerabilities/spec_store_bypass
> Mitigation: Speculative Store Bypass disabled
> Darkstar ~ # cat /sys/devices/system/cpu/vulnerabilities/spectre_v1
> Mitigation: __user pointer sanitization
> Darkstar ~ # cat /sys/devices/system/cpu/vulnerabilities/spectre_v2
> Mitigation: Full AMD retpoline, IBPB: always-on, STIBP: disabled, RSB
> filling

Corbin



  parent reply	other threads:[~2019-07-17  3:25 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12 12:18 [gentoo-user] AMD microcode updates - where are they?! Mick
2019-07-12 16:07 ` [gentoo-user] " Ian Zimmerman
2019-07-13  0:56   ` Adam Carter
2019-07-13  1:13     ` Adam Carter
2019-07-13 10:04       ` Mick
2019-07-13 10:01     ` Mick
2019-07-13 16:21 ` [gentoo-user] " Jack
2019-07-13 17:18   ` Mick
2019-07-13 17:23     ` Mick
2019-07-13 17:42     ` Jack
2019-07-13 18:06       ` Mick
2019-07-13 18:16         ` Corbin
2019-07-13 19:23           ` Mick
2019-07-13 20:16             ` Wols Lists
2019-07-13 21:01               ` Rich Freeman
2019-07-13 22:03                 ` Mick
2019-07-14 13:26                   ` Mick
2019-07-15  0:42                     ` Adam Carter
2019-07-17  3:21                     ` Corbin [this message]
2019-07-17 10:58                       ` Mick
2019-07-17 12:46                         ` Corbin
2019-07-17 20:51                           ` [gentoo-user] " Ian Zimmerman
2019-07-18 12:33                             ` Corbin
2019-07-18 18:23                               ` Mick
2019-07-17 23:38                         ` [gentoo-user] " Adam Carter
2019-07-15  4:30         ` [gentoo-user] " Ian Zimmerman
2019-07-15 21:18           ` Ian Zimmerman
2019-07-16  9:47             ` Mick
2019-07-15  5:15         ` [gentoo-user] " Adam Carter
2019-07-16  8:10     ` Neil Bothwick

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=fda97826-df7f-fdd8-65d7-2a8d1bf7bf5d@charter.net \
    --to=corbinbird@charter.net \
    --cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox