From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx3-rdu2.redhat.com ([66.187.233.73] helo=mx1.redhat.com) by Galois.linutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1f8oba-0003vM-KT for speck@linutronix.de; Wed, 18 Apr 2018 17:02:43 +0200 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 109B58D77C for ; Wed, 18 Apr 2018 15:02:36 +0000 (UTC) Received: from washington.bos.jonmasters.org (ovpn-121-132.rdu2.redhat.com [10.10.121.132]) by smtp.corp.redhat.com (Postfix) with ESMTPS id D4F861C723 for ; Wed, 18 Apr 2018 15:02:35 +0000 (UTC) Subject: [MODERATED] Re: GPZv4 References: <67ef414c-f57c-0300-973b-f8898ee4d3b1@redhat.com> <20180418024816.GA6450@localhost.localdomain> <071ce2ea-c47d-9ae7-3e66-2e14ee32b97a@redhat.com> <1c1c86c5-664b-42a4-44bb-fd8853a55e41@redhat.com> <20180418145216.GB9939@localhost.localdomain> From: Jon Masters Message-ID: <560c94a1-41c4-f03f-d89f-9298b282b4eb@redhat.com> Date: Wed, 18 Apr 2018 11:02:35 -0400 MIME-Version: 1.0 In-Reply-To: <20180418145216.GB9939@localhost.localdomain> Content-Type: multipart/mixed; boundary="us3ZfJ8iKzvrK1JmRyEDA1I4kUoujJXqF"; protected-headers="v1" To: speck@linutronix.de List-ID: This is an OpenPGP/MIME encrypted message (RFC 4880 and 3156) --us3ZfJ8iKzvrK1JmRyEDA1I4kUoujJXqF Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 04/18/2018 10:52 AM, speck for Konrad Rzeszutek Wilk wrote: > On Wed, Apr 18, 2018 at 10:07:44AM -0400, speck for Jon Masters wrote: >> On 04/18/2018 10:04 AM, speck for Thomas Gleixner wrote: >>> On Wed, 18 Apr 2018, speck for Jon Masters wrote: >>>> On 04/18/2018 04:54 AM, speck for Thomas Gleixner wrote: >>>>> On Tue, 17 Apr 2018, speck for Konrad Rzeszutek Wilk wrote: >>>>>> 2). SBB vs MDD vs SBBD. >>>>>> >>>>>> MDD =3D Memory Disambiguation Disable >>>>>> SBB =3D Speculative Store Bypass >>>>>> SBBD =3D Speculative Store Bypass Disable >>>>>> >>>>>> Thomas likes 'MDD', Jon likes 'SBB', but he is also fine with 'SBB= D'. >>>>> >>>>> I'm fine with SBBD as well. It's the same semantics as the other kn= obs as >>>>> it controls the mitigation. >>>> >>>> Great. Might I recommend keeping what I sent to Konrad (both mdd and= >>>> ssbd recognized), but do whichever you like Konrad ;) >>>> >>>>> So can we for now just start with the minimal set of auto, off, on = and then >>>>> hash out the prctl or not question. The big hammer is the most impo= rtant >>>>> piece we need to have ready for merging when the embargo is lifted.= >>>> >>>> I've sent the big hammer patches last night. Konrad's original set w= ith >>>> a few fixes, and just does "auto", "off", "on", and tested working o= k. >>> >>> Can we please have proper mail submitted patches? These tarballs are = a >>> PITA. >> >> Leaving the ball with Konrad to review/post when he's happy. >=20 > Sure thing. Will crank on them tonight/tomorrow morning. And tomorrow > night or Friday folks can rip in them. >=20 > Will post them as v2! Great. Paolo is pondering the KVM side of things some more - we just synced up on a few concerns I've got around exposing SPEC_CTRL. Due to how Intel did this for guests, of course a guest can be started with MD set but then whack it because it's not aware of that bit. From a Linux PoV this is why I suggested a todo (feel free to incorporate if you like) that x86_spec_ctrl_base be initially set at boot with an rdmsr. Then we'd at least preserve additional new bits that are added later. For other OSes, it might be we end up with a trapping solution for those who want to be able to override a guest's view of MD if Intel can't be persuaded to make MD lockable or something (as Paolo said, shadowing is probably overkill/not possible at this point). Jon. --=20 Computer Architect | Sent from my Fedora powered laptop --us3ZfJ8iKzvrK1JmRyEDA1I4kUoujJXqF--