From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Google-Smtp-Source: AH8x227HK1THY0O1TZuntQBo3e1aH+xAKdNVmZVZYglIVJbRvOpcle6yhHG98hkMQsHytUiI6J2c ARC-Seal: i=1; a=rsa-sha256; t=1516968995; cv=none; d=google.com; s=arc-20160816; b=Iehc/Lp/DftuyPKbyXSMLmfsd/xYv/htbxfuP9vVsSXAnLgmw8JM1IQAqks8wC7Ic8 nfNY2m6Nd6M0z2KtZsAm4IQd6yh/aL8U/Wg+6rqQkBbvrMG4PPUxl0m2Wc9l4zqRVeOa WJc/NYZOpezwQhn7LIeV2h2m+Kofnodx6RwTnoiG2O9naiBRgnH6foriYcYME+OET4s5 I3dJ7BjPO15/nHkkemJA6DyLrhcILvfri/S7slIxie9OeujwAOhOrF85DOQjnCFWqbvX E0Eh2J2OVrAwucnSGMzMoaHttBoeHHHygVl8NBJtoLFpDqnprk9rPjasISqcl+iC63tb 44Pw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=mime-version:references:in-reply-to:date:to:from:subject:message-id :arc-authentication-results; bh=8r5Q1r08UfE5N6RHtyhX8AaVHlTGQggl2Pbjh75vKuo=; b=sd4aFMvGbytjn2uulwng3UeNPMvDLkh3k9RPfyBbrfI+EF4wnmA1lciEYe0UyW02YS /VQPo3Xr1/XOBJUgDNR4sideN3uCNVYSzji192q7Oqme+B6Q12UwcJv6zeKzEwu/GUmU Xl4WHgA7tW4CYPnBMLzMH0FpL+F3SGjj806Mo5IVnFzpZHR9GLPBmUdIXmSBaZAqwNr0 Dn4VwGMgRHyTLk/UsNENETe0QQZJMWecgFfIiXmw8vomygqfuhioJ3So582WJEqBl7az FImL+tdEeDaXZ4dcOgy78vMUUp6rYLGVB+mEHWcgXKZopoFKcivhdcVqa9coISwDyWJ+ GIDg== ARC-Authentication-Results: i=1; mx.google.com; spf=neutral (google.com: 78.194.244.226 is neither permitted nor denied by best guess record for domain of corsac@debian.org) smtp.mailfrom=corsac@debian.org Authentication-Results: mx.google.com; spf=neutral (google.com: 78.194.244.226 is neither permitted nor denied by best guess record for domain of corsac@debian.org) smtp.mailfrom=corsac@debian.org Message-ID: <1516968989.19619.8.camel@debian.org> Subject: Re: [PATCH v3 6/6] x86/cpufeature: Blacklist SPEC_CTRL on early Spectre v2 microcodes From: Yves-Alexis Perez To: David Woodhouse , arjan@linux.intel.com, tglx@linutronix.de, 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 Date: Fri, 26 Jan 2018 13:16:29 +0100 In-Reply-To: <1516813025-10794-7-git-send-email-dwmw@amazon.co.uk> References: <1516813025-10794-1-git-send-email-dwmw@amazon.co.uk> <1516813025-10794-7-git-send-email-dwmw@amazon.co.uk> Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-ddkDd+XxWGIlk1S5j+Gq" X-Mailer: Evolution 3.26.3-1 Mime-Version: 1.0 X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: =?utf-8?q?1590493767497033665?= X-GMAIL-MSGID: =?utf-8?q?1590657281316418466?= X-Mailing-List: linux-kernel@vger.kernel.org List-ID: --=-ddkDd+XxWGIlk1S5j+Gq Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, 2018-01-24 at 16:57 +0000, David Woodhouse wrote: > We don't refuse to load the affected microcodes; just refuse to use SPEC_= CTRL > if they're detected. Hi David, Are we sure those microcodes instability are only related to SPEC_CTRL? Regards, --=20 Yves-Alexis --=-ddkDd+XxWGIlk1S5j+Gq Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlprHB0ACgkQ3rYcyPpX RFvmMwf9GP18Dflf5xlMbCqS62UHLfwM+RZK2tCXddWAsM/K7c/9gBr2n9w/YNm2 +g8L4UwBDNGwLjin7YZnddK2/DBGQPvdZsZgPH3p43qJiHtAm7qMB2xHcyg+ZnfM rOLEbvlBTRENUa4L3FOr044rrUNXB7hAX7QjRq7L+FQQMXrkf3iJV5Gs5KEPen9l a2AIHHjG6/gSqbJbjEpGQyOcuNE8oN7GUqQGDjDdChmsZ57CIeiQc0VsthHdYKQz 7w2F8mPdN6bV2p1U1YFyAZmiIy2aa36SBc2DCR7oHO9yGaK2jK6aNAo5nlFbdBUR C+WTcYjpOqfVgzY45FA8K7G8YF/3HA== =uob4 -----END PGP SIGNATURE----- --=-ddkDd+XxWGIlk1S5j+Gq--