From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754737AbeAGVth (ORCPT + 1 other); Sun, 7 Jan 2018 16:49:37 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:47884 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754693AbeAGVtg (ORCPT ); Sun, 7 Jan 2018 16:49:36 -0500 Message-Id: <20180107214759.387300853@linutronix.de> User-Agent: quilt/0.63-1 Date: Sun, 07 Jan 2018 22:47:59 +0100 From: Thomas Gleixner To: LKML Cc: Linus Torvalds , Greg Kroah-Hartman , Ingo Molnar , Peter Zijlstra , Borislav Petkov , David Woodhouse , Dave Hansen , Will Deacon Subject: [patch V2 0/2] sysfs/cpu: Implement generic vulnerabilites directory Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: The meltdown/spectre vulnerabilities affect several architectures and people are asking for a common way to figure out whether a system is affected or not. Create /sys/devices/system/cpu/vulnerabilites and the files /sys/devices/system/cpu/vulnerabilites/meltdown /sys/devices/system/cpu/vulnerabilites/spectre_v1 /sys/devices/system/cpu/vulnerabilites/spectre_v2 Add the x86 implementation which shows: meltdown Mitigation: PTI spectre_v1 Vulnerable sepctre_v1 Vulnerable On an AMD CPU the output of meltdown is: Not affected. If PTI is turned off and the CPU is affected of meltdown the output becomes: Vulnerable That series applies on top of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/pti V1 -> V2: Add documentation and use sprintf Thanks, tglx