Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Tue, 28 Aug 2018 12:27:04 +0200 (CEST)
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?
Message-ID: <alpine.LSU.2.21.1808281225550.27853@er-systems.de>
User-Agent: Alpine 2.21 (LSU 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


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