From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Google-Smtp-Source: AH8x227jGOb5OdDZZMdFBWiO7nsdsJBnNR/Dm1k70lKQ6RzDuGsr4HxRW63PnEH3dmzL1CUevEst ARC-Seal: i=1; a=rsa-sha256; t=1516897506; cv=none; d=google.com; s=arc-20160816; b=dhSg1ctKmRMq0PF8OAaUMqHKR/AJ8Z9gOeC0R8ZNcYLKPqHnnFSKLmmQYxD7HO5VU3 Eu6ma2r8bNSWX4IMRwclIKs9Eicn4mcAtMAbzBNEyEcJeCGNUatrmZhMl1zHbMYcGCaj chCWTJwZ5bE7M394ywoyvBfjbqplJUof6iwb7oCvI/+IcV5Xa0N6+HubXTUyuoz1IgMC mqVE47dMpo0RqHaND6teSLNrYmTT7Zk7CgzLpZId3vbUeR/Ry9pWqimCXbsjLHBEDfPv EVzopuRGgmzG68fMF2yqQ392zmL4RduLKk57fZm6O3RgNGtareAF1UaTGNGoDRTKF/wt Tofg== 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=Q6nNmtAzzYp8zsM6CND9y2dviFDWpanzAFC4cnxJvys=; b=lGK23TpvCz00OiNQ6OzffNadcBhV8Rdi+Fd82oX4YfoIshpA9hkG6nRPc63MTaol9y uDcTJwEJj9NZoRD7rZH0caU8d7dUdyAG8DP9I7DzeEGz2zfz70wDPwErpt5+P3zw1lFA wud/KvOB0KgVbeJyArUTnm/fJEXPRwVtAImvH3EQ1ffx0p0deHOGl+yLmpIj0Ost+mgq 2RrhO0wSxEoPvjuNjPMc+xZ1ZYt5Ns1d7jIvo8X8ogjsYhDSKGlquBIFZ0JhIcKrVzoB ms/LJb8JapL/75TgB1bJmMForrKNNjw/AiQNVK5lkDV1K42F5DWNg34f9c0gnqH3atRW 0tvQ== 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 17:24:49 +0100 (CET) From: Thomas Gleixner To: Alan Cox cc: David Woodhouse , 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, 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: <20180125161547.33e63bb3@alans-desktop> 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> <20180125161547.33e63bb3@alans-desktop> 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?1590582319113184928?= X-Mailing-List: linux-kernel@vger.kernel.org List-ID: On Thu, 25 Jan 2018, Alan Cox wrote: > > Here's what I have now. I'm happy enough with this, so the main thing > > I'm looking for is an ack from Alan for patch #5 of the series, if I've > > got that sufficiently correct now. > > You have my ACK for patch 5: Any further changes I'll submit as updates > once it's merged. > > I am happy with patch 5 and I think for 64bit we are probably done for > the mainstream. VIA/Centaur data would be nice. > > The microcode otoh I don't think makes sense - do you want to be secure > with a slightly higher risk of crashes or insecure ? Once you can point > at a newer ucode for each case then yes I personally at least think it > then makes sense to tell users they want the newer one. Yes, ideally we can tell the user to update to ucode rev > X for a particular SKU. Though with the current state of affairs all we can do is accumulate ucode revisions which are marked bad by Intels Quality Assumptions at a given day. Once Intel gets its act together and provides authoritative information we can revisit this and make it user friendly. You might be able to speculate more precisely when this is going to happen. Thanks, tglx