public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Adam Carter <adamcarter3@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] AMD microcode updates - where are they?!
Date: Mon, 15 Jul 2019 10:42:15 +1000	[thread overview]
Message-ID: <CAC=wYCGNj=B9tSqiep3=i9H5Xi0ekX7uQXi+rd+Y+BoN=p-1FA@mail.gmail.com> (raw)
In-Reply-To: <21714265.1ZXtKVbesA@localhost>

[-- Attachment #1: Type: text/plain, Size: 1673 bytes --]

> 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.


Sounds reasonable, but the 15h code was updated mid 2018, so unless the cpu
or BIOS update is from after then, i would be concerned.

If your APUs return similar to this then then there's nothing to worry about

# grep . /sys/devices/system/cpu/vulnerabilities/*
/sys/devices/system/cpu/vulnerabilities/l1tf:Not affected
/sys/devices/system/cpu/vulnerabilities/mds:Not affected
/sys/devices/system/cpu/vulnerabilities/meltdown:Not affected
/sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Mitigation:
Speculative Store Bypass disabled via prctl and seccomp
/sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: __user
pointer sanitization
/sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full AMD
retpoline, IBPB: conditional, STIBP: disabled, RSB filling

[-- Attachment #2: Type: text/html, Size: 2183 bytes --]

  reply	other threads:[~2019-07-15  0:42 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 [this message]
2019-07-17  3:21                     ` Corbin
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='CAC=wYCGNj=B9tSqiep3=i9H5Xi0ekX7uQXi+rd+Y+BoN=p-1FA@mail.gmail.com' \
    --to=adamcarter3@gmail.com \
    --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