From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx2.suse.de ([195.135.220.15]) by Galois.linutronix.de with esmtps (TLS1.0:DHE_RSA_CAMELLIA_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1fA0h4-00051G-ME for speck@linutronix.de; Sun, 22 Apr 2018 00:09:19 +0200 Received: from relay2.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id CCA30ADD5 for ; Sat, 21 Apr 2018 22:09:11 +0000 (UTC) Date: Sun, 22 Apr 2018 00:09:03 +0200 From: Borislav Petkov Subject: [MODERATED] Re: [patch 07/11] [PATCH v2 07/10] Linux Patch #7 Message-ID: <20180421220903.GE18575@pd.tnic> References: <20180420022613.270943302@localhost.localdomain> <20180420174242.GO13977@pd.tnic> <20180421032701.GA4490@localhost.localdomain> <20180421090345.GA18575@pd.tnic> <20180421122117.GA5337@localhost.localdomain> <20180421192509.GD18575@pd.tnic> MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable To: speck@linutronix.de List-ID: On Sat, Apr 21, 2018 at 02:41:13PM -0700, speck for Linus Torvalds wrote: > At the risk of bike shedding, can we *please* just write out "Store buffer = > bypass" and "Memory disambiguation" instead of using SBB amd MD? >=20 > The patches aren't so big, and these names won't be used so much that we=20 > can't use longer names. Yes, yes, we use PTI for the page table isolation, = > but that had a much wider impact. For Spectre v1 we at least use _half_=20 > words like "nospec". >=20 > Maybe even X86_FEATURE_STBUF_BYPASS? >=20 > And X86_FEATURE_STBUF_BYPASS_MITIGATE? So those strings after X86_FEATURE will land in /proc/cpuinfo and traditionally, we have kept the feature names there abbreviated. Well, at least most of them. The only feature where this matters, though, is the memory disambiguation feature which should be in /proc/cpuinfo, IMO, so should we call it X86_FEATURE_MEM_DISAMBG or so? /proc/cpuinfo will have then "mem_disambg" or we can put the string we wanna have in "": #define X86_FEATURE_MEM_DISAMBG ... /* "string_we_wanna_have" memory disambi= guation */ The remaining ones are synthetic ones and they can be as long as we want them to be as we won't show them in /proc/cpuinfo. The current state of the mitigation will be, as with the other bugs, in /sys/devices/system/cpu/vulnerabilities/ --=20 Regards/Gruss, Boris. SUSE Linux GmbH, GF: Felix Imend=C3=B6rffer, Jane Smithard, Graham Norton, HR= B 21284 (AG N=C3=BCrnberg) --=20