From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Google-Smtp-Source: AH8x226NPsFi9MDYUR5VXlLTn7UjdKo1T95EkswTMz9cA72eEHRuKzBrGTseXotHcRqh6VMlKwiR ARC-Seal: i=1; a=rsa-sha256; t=1516892332; cv=none; d=google.com; s=arc-20160816; b=vMN9eL2xogRG1HycJp+ZTf4t9ciupOKVdzFquo29J+dOty0u4EEaDuForZuszXrVWq nF8Y7rzvbviE4kfOfJ8ImKmtoIYHQb4ALNplPRHSC3h9E3bi2+ItNl0pVfgIQmeJgi/C 0Vb3XeX+PfKzTDqV2np5Oxycww6MyHPop3Y9owuvvN56HDAtSbJmMjcsIuAu0zRnNUxk rNNkqGdET/BvKg3vfg19NxlEH2FNAcqwhFAQGr4nbe93M/bdvKqYuhunJWjF6gxObroK r5QiVJoZ3Uuz86GMF4QifKgAxi8sfTpyeeOUOuz8zcuPoHOal9FLt6dj4sGVgxc+0uJf O1HA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=mime-version:user-agent:references:message-id:in-reply-to:subject :cc:to:from:date:arc-authentication-results; bh=1SzivvP9bDFDcsw1rgELmLIruol6IiSPFCG6FGczBLM=; b=XOmgX6wNK1sxaJ27KErWNJ11sqXr/DRQGJQtls8VMVXMKCidWbOke+X4EhObaL6lb7 kbuq0P2hOIw7zlBR5WrNuxn6aZRZz76zRr0QH6S4R4YRhMvH+LRjQ5Y32KK4eghC4WgA 76KPPqHL+k4BLLJ6meDnGvxEBs0BCkrEknlSd6cr4Iob+o8NDwpECdRaXme8JrkYxliQ 4STPT6ljKg3EEX4I0TlMpes5YZoPJbCx+okpsaJL02mmWV3TMwlh4bimtSrLd5Be/AGn 8euyoxGADFeUMxXOxWfiGHNTX/iSgc7lZq8zu/3PCe8mQfsm8pu/hzZcRE+8TXpGthqc kzUA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of tglx@linutronix.de designates 2a01:7a0:2:106d:700::1 as permitted sender) smtp.mailfrom=tglx@linutronix.de Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of tglx@linutronix.de designates 2a01:7a0:2:106d:700::1 as permitted sender) smtp.mailfrom=tglx@linutronix.de Date: Thu, 25 Jan 2018 15:58:35 +0100 (CET) From: Thomas Gleixner To: David Woodhouse cc: arjan@linux.intel.com, karahmed@amazon.de, x86@kernel.org, linux-kernel@vger.kernel.org, tim.c.chen@linux.intel.com, bp@alien8.de, peterz@infradead.org, pbonzini@redhat.com, ak@linux.intel.com, torvalds@linux-foundation.org, gregkh@linux-foundation.org, dave.hansen@intel.com, gnomes@lxorguk.ukuu.org.uk, ashok.raj@intel.com, mingo@kernel.org Subject: Re: [PATCH v4 6/7] x86/cpufeature: Blacklist SPEC_CTRL on early Spectre v2 microcodes In-Reply-To: <1516887714.30244.121.camel@infradead.org> Message-ID: References: <1516872189-16577-1-git-send-email-dwmw@amazon.co.uk> <1516872189-16577-7-git-send-email-dwmw@amazon.co.uk> <1516876994.30244.51.camel@infradead.org> <1516879213.30244.74.camel@infradead.org> <1516887714.30244.121.camel@infradead.org> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: =?utf-8?q?1590555855308082400?= X-GMAIL-MSGID: =?utf-8?q?1590576894534428345?= X-Mailing-List: linux-kernel@vger.kernel.org List-ID: On Thu, 25 Jan 2018, David Woodhouse wrote: > On Thu, 2018-01-25 at 12:34 +0100, Thomas Gleixner wrote: > > > > This stuff is really a master piece of trainwreck engineering. > > > > So yeah, whatever we do we end up with a proper mess. Lets go for a > > blacklist and hope that we'll have something which holds at some > > foreseeable day in the future. > > > > The other concern I have is IBRS vs. IBPB. Are we sufficiently sure that > > IBPB is working on those IBRS blacklisted ucode revisions? Or should we > > just play safe and not touch any of this at all when we detect a > > blacklisted one? > > That isn't sufficiently clear to me. I've changed it back to blacklist > *everything* for now, to be safe. If at any point Intel want to get > their act together and give us coherent information to the contrary, we > can change to separate IBPB/IBRS blacklists. Thanks for that. That's the only sensible approach as long as we have to deal with the current Quality Assumptions... Thanks, tglx