From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A7CDCC433F4 for ; Tue, 28 Aug 2018 10:37:16 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6B52620878 for ; Tue, 28 Aug 2018 10:37:16 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 6B52620878 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=lio96.de Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727618AbeH1O2O (ORCPT ); Tue, 28 Aug 2018 10:28:14 -0400 Received: from er-systems.de ([148.251.68.21]:57450 "EHLO er-systems.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727067AbeH1O2O (ORCPT ); Tue, 28 Aug 2018 10:28:14 -0400 X-Greylist: delayed 607 seconds by postgrey-1.27 at vger.kernel.org; Tue, 28 Aug 2018 10:28:13 EDT Received: from localhost.localdomain (localhost [127.0.0.1]) by er-systems.de (Postfix) with ESMTP id 4A5A2D60115; Tue, 28 Aug 2018 12:27:05 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by er-systems.de (Postfix) with ESMTPS id 2B24CD60109; Tue, 28 Aug 2018 12:27:05 +0200 (CEST) Date: Tue, 28 Aug 2018 12:27:04 +0200 (CEST) From: Thomas Voegtle X-X-Sender: thomas@er-systems.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: User-Agent: Alpine 2.21 (LSU 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-Virus-Status: No X-Virus-Checker-Version: clamassassin 1.2.4 with clamdscan / ClamAV 0.100.1/24880/Tue Aug 28 06:46:22 2018 signatures 58. Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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