From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Google-Smtp-Source: AH8x225CTpmEAhQzqskeyXQ9nzQ4tAwoU4FztUmqHGB1iNqzbXMIRybFm+DWCUq12YGK1sS86Q5W ARC-Seal: i=1; a=rsa-sha256; t=1517317888; cv=none; d=google.com; s=arc-20160816; b=XKnZHcbVQOu+2AYFgdU4RfskYtRyiasFqHYKKzQBqUzkRJNBV/U/RY+tzaeOTc2srs cfy0yyVUeCfo5ksEbQWq4Pm2N/99akRnK+ys0DBMkeZoT9o4BAS8SodkruBiwepfUb1m g9DW6OU/WzLUN9YWp2BYevmxEiZGg9SmmAdsV43Wlopb9HF1liypNsxvCSHNZTJhWeO7 XQm5oXr8bugWjAL98PryNTw5pQxs8+NQEVu6UBmqCr5G53A7dy6Yvji9FlsjQCtW5BGs zeEzcLpEf6efQ0p+d45ZZlYz2uYqJ6+9QPPZgSldVQUB7OUTsoWmqodXXb5Ps+xmmnik C5ow== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:arc-authentication-results; bh=bWnrMM2CByBWyEbzYciYg6MRr5sRi6VZUCuW8T1l3Lg=; b=F120WsYpZJMY2x56tKgBdyx9o097KCfVjP6/EJVI/+SZViARoFS1w6EWUGcMdX3Mq4 YbswVrBhYeYO6NmpQ0iAb5qiy2T7FxoUZLOxtdmdufSEDDDR9ml1aH0lpUfjyxd6Zqp+ l34fuypS/MXlchmlBpSaHlYqbcoU1m/+TcdmwY8XrTz+S3Q3DAkOHQEihXaqUEKqtHTl D/pxEilWI9miZBgM6TVOmrs4ARx3fR0i0V3WtSpbzijtbEHM5JCp5nXeyuBREwhulmDZ 5T4U3dXjPBU2k2U3gL1XNOE8un02HZO7jYDJQnuFOz/C319AzzASJPGzLfaPaY5b6sSe 1QFA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of bp@alien8.de designates 5.9.137.197 as permitted sender) smtp.mailfrom=bp@alien8.de Authentication-Results: mx.google.com; spf=pass (google.com: domain of bp@alien8.de designates 5.9.137.197 as permitted sender) smtp.mailfrom=bp@alien8.de Date: Tue, 30 Jan 2018 14:11:22 +0100 From: Borislav Petkov To: Thomas Gleixner Cc: David Woodhouse , arjan@linux.intel.com, karahmed@amazon.de, x86@kernel.org, linux-kernel@vger.kernel.org, tim.c.chen@linux.intel.com, peterz@infradead.org, pbonzini@redhat.com, ak@linux.intel.com, torvalds@linux-foundation.org, gregkh@linux-foundation.org Subject: Re: [PATCH] x86/cpuid: Fix up "virtual" IBRS/IBPB/STIBP feature bits on Intel Message-ID: <20180130131122.s3bs6lbs43go73gj@pd.tnic> References: <1517269773-16750-1-git-send-email-dwmw@amazon.co.uk> <20180130105814.m5zd43dyx2o2ius2@pd.tnic> <1517310230.18619.86.camel@infradead.org> <20180130111848.zjv2dngfzcz35lyt@pd.tnic> <1517311693.18619.102.camel@infradead.org> <1517314193.18619.115.camel@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170609 (1.8.3) X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: =?utf-8?q?1590972687399963990?= X-GMAIL-MSGID: =?utf-8?q?1591023122499292409?= X-Mailing-List: linux-kernel@vger.kernel.org List-ID: On Tue, Jan 30, 2018 at 01:57:21PM +0100, Thomas Gleixner wrote: > So much for the theory. That's not going to work. If the boot cpu has the > feature then the alternatives will have been applied. So even if the flag > mismatch can be observed when a secondary CPU comes up the outcome will be > access to a non existing MSR and #GP. Yes, with mismatched microcode we're f*cked. So my question is: is there such microcode out there or is this something theoretical which we want to address? (.. and adressing this will be ugly, no matter what.) And if I were able to wish, I'd like to blacklist that microcode in dracut so that it doesn't come anywhere near my system. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.