mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Voegtle <tv@lio96.de>
To: x86@kernel.org, linux-kernel@vger.kernel.org, tglx@linutronix.de,
	mingo@redhat.com
Subject: Apollo Lake with newer microcode: not affected by meltdown anymore?
Date: Tue, 28 Aug 2018 12:27:04 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LSU.2.21.1808281225550.27853@er-systems.de> (raw)


Hello,

Kernel 4.18.5 with old microcode:

[    0.000000] microcode: microcode updated early to revision 0x2c, date =
2017-03-25
cat /sys/devices/system/cpu/vulnerabilities/meltdown
Mitigation: PTI


Kernel 4.18.5 with new microcode (microcode-20180807.tgz), same config:

[    0.000000] microcode: microcode updated early to revision 0x32, date =
2018-05-11
cat /sys/devices/system/cpu/vulnerabilities/meltdown
Not affected


This happens with 4.14.y and 4.9.y as well.

The same with ssb:
old microcode: spec_store_bypass:Vulnerable
new microcode: spec_store_bypass:Not affected

Is this intentional behavior? I have never seen this on other CPUs, such
as Gemini Lake or Baytrail, Haswell etc.

This is a Lenovo Ideapad 120S-11IAP with Apollo Lake N3350 (Goldmont)


    Thomas



             reply	other threads:[~2018-08-28 10:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28 10:27 Thomas Voegtle [this message]
2018-08-28 10:37 ` Thomas Gleixner
2018-08-28 12:35   ` Thomas Voegtle

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=alpine.LSU.2.21.1808281225550.27853@er-systems.de \
    --to=tv@lio96.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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
all inboxes | Powered by JetHome®