From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from userp2120.oracle.com ([156.151.31.85]) by Galois.linutronix.de with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1f9YQY-0000DK-Iy for speck@linutronix.de; Fri, 20 Apr 2018 17:58:23 +0200 Received: from pps.filterd (userp2120.oracle.com [127.0.0.1]) by userp2120.oracle.com (8.16.0.22/8.16.0.22) with SMTP id w3KFuqvC086158 for ; Fri, 20 Apr 2018 15:58:15 GMT Received: from userv0022.oracle.com (userv0022.oracle.com [156.151.31.74]) by userp2120.oracle.com with ESMTP id 2hdrxpdbnq-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Fri, 20 Apr 2018 15:58:15 +0000 Received: from aserv0122.oracle.com (aserv0122.oracle.com [141.146.126.236]) by userv0022.oracle.com (8.14.4/8.14.4) with ESMTP id w3KFwE6O032149 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Fri, 20 Apr 2018 15:58:14 GMT Received: from abhmp0018.oracle.com (abhmp0018.oracle.com [141.146.116.24]) by aserv0122.oracle.com (8.14.4/8.14.4) with ESMTP id w3KFwEOH010415 for ; Fri, 20 Apr 2018 15:58:14 GMT Date: Fri, 20 Apr 2018 11:58:09 -0400 From: Konrad Rzeszutek Wilk Subject: [MODERATED] Re: [patch 06/11] [PATCH v2 06/10] Linux Patch #6 Message-ID: <20180420155804.GA808@localhost.localdomain> References: <20180420022613.203909041@localhost.localdomain> <20180420112116.GL4064@hirez.programming.kicks-ass.net> <491430fb-c47a-5335-2b43-67c625901fb0@redhat.com> MIME-Version: 1.0 In-Reply-To: <491430fb-c47a-5335-2b43-67c625901fb0@redhat.com> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: speck@linutronix.de List-ID: On Fri, Apr 20, 2018 at 11:33:05AM -0400, speck for Jon Masters wrote: > (your mail was unreadable by enigmail on Thunderbird for some reason, > manually extracted using GPG, excuse any copy+paste errors below) Use mutt :-) > > On 04/20/2018 07:21 AM, speck for Peter Zijlstra wrote: > On Thu, Apr 19, 2018 at 10:25:46PM -0400, speck for konrad.wilk_at_oracle.c= > om wrote: > >> We provide two sets of knobs. The first are x86 specific: > >> > >> nomdd > >> mdd=3D[off,auto,on] > >> > >> We also support cross-architecture versions of these: > >> > >> nossbd > >> ssbd=3D[off,auto,on] > > > So why does x86 have to be different? Can't it simply use the generic > > named ones? I didn't see a rationale for that. > > x86 doesn't have to be different. I originally proposed keeping also > "mdd" just to keep everyone happy on the x86 side in case they cared. > But "ssbd" is a nice industry neutral term and also works for x86. It > also will fit with the language that Google will use in their text. Ugh, another web-page. ssbdattack.com? Let me rip out the mdd from the documentation and the code.