From: Adam Carter <adamcarter3@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Kernel 4.14.14 has meltdown / spectre info in /sys
Date: Fri, 19 Jan 2018 10:50:25 +1100 [thread overview]
Message-ID: <CAC=wYCEg-qTgODh+zdn17f9Evj7fELwgC-GUbtxN_tCeYZzbTA@mail.gmail.com> (raw)
In-Reply-To: <20180118221718.kqxsivj3av3bc3eb@matica.foolinux.mooo.com>
[-- Attachment #1: Type: text/plain, Size: 618 bytes --]
On Fri, Jan 19, 2018 at 9:17 AM, Ian Zimmerman <itz@very.loosely.org> wrote:
>
> matica!13 linux$ dmesg | fgrep -i phenom
> [ 0.603608] smpboot: CPU0: AMD Phenom(tm) II X4 955 Processor
> (family: 0x10, model: 0x4, stepping: 0x3)
>
> Looking at the kernel source (for 4.9.77), the flag is initially set no
> matter what in arch/x86/kernel/cpu/common.c @cpu_show_meltdown(), and
> nothing afterwards clears it ...
With 4.14.14, pretty much same CPU;
model : 4
model name : AMD Phenom(tm) II X4 965 Processor
stepping : 3
$ cat /sys/devices/system/cpu/vulnerabilities/meltdown
Not affected
[-- Attachment #2: Type: text/html, Size: 1157 bytes --]
next prev parent reply other threads:[~2018-01-18 23:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 8:28 [gentoo-user] Kernel 4.14.14 has meltdown / spectre info in /sys Adam Carter
2018-01-18 18:31 ` [gentoo-user] " Nikos Chantziaras
2018-01-29 9:19 ` [gentoo-user] PSA: GCC 7.3 allows to build kernel with full Spectre v2 mitigation Nikos Chantziaras
2018-01-29 15:02 ` Rich Freeman
2018-01-18 19:31 ` [gentoo-user] Re: Kernel 4.14.14 has meltdown / spectre info in /sys Ian Zimmerman
2018-01-18 20:43 ` Rich Freeman
2018-01-18 21:21 ` Adam Carter
2018-01-18 21:22 ` Adam Carter
2018-01-18 22:17 ` Ian Zimmerman
2018-01-18 23:50 ` Adam Carter [this message]
2018-01-24 21:51 ` Ian Zimmerman
2018-01-25 6:39 ` Adam Carter
2018-01-25 12:43 ` Rich Freeman
2018-01-22 1:41 ` Corbin Bird
2018-01-22 2:11 ` Rich Freeman
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=wYCEg-qTgODh+zdn17f9Evj7fELwgC-GUbtxN_tCeYZzbTA@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