[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: kernel 4.14.15 compilation using GCC 8 in unstable.......





On 26 January 2018 at 22:59, Michael Lange <klappnase@freenet.de> wrote:
On Fri, 26 Jan 2018 23:41:07 +0100
Michael Lange <klappnase@freenet.de> wrote:

> When I check /proc/cpuinfo I see that "msr" is listed in the "flags"
> section. So why doesn't the driver load automagically?
> But then, at least with the version of the checker-script here, it
> doesn't seem to make any difference, at least for whatever the script
> tries.
> Don't know if enabling msr will do me any good otherwise.

Update:
just checked with my laptop (Intel/Baytrail); it is the same with msr,
module not loaded automatically, when loaded manually the contents
of /dev/cpu/0 look just as on my AMD desktop machine. The output of the
checker script still says "No" in the lines referring to msr.
*BUT*, since I finally managed to compile 4.15.rc9 with gcc-7.3, the
script claims the laptop is no longer vulnerable to "Spectre2".
I think I'll count that as success and call it a night now :-)

​You could run this command:​


​djt /home/mikef # !424
grep . /sys/devices/system/cpu/vulnerabilities/*
/sys/devices/system/cpu/vulnerabilities/meltdown:Not affected
/sys/devices/system/cpu/vulnerabilities/spectre_v1:Vulnerable
/sys/devices/system/cpu/vulnerabilities/spectre_v2:Vulnerable: Minimal AMD ASM retpoline


or use the checker (I assume you already are)

https://github.com/speed47/spectre-meltdown-checker

Cheers

MF




 

Best regards

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

I realize that command does have its fascination, even under
circumstances such as these, but I neither enjoy the idea of command
nor am I frightened of it.  It simply exists, and I will do whatever
logically needs to be done.
                -- Spock, "The Galileo Seven", stardate 2812.7



Reply to: