Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751942AbeAEOya (ORCPT + 1 other); Fri, 5 Jan 2018 09:54:30 -0500 Received: from pic75-3-78-194-244-226.fbxo.proxad.net ([78.194.244.226]:57628 "EHLO mail.corsac.net" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1751875AbeAEOy3 (ORCPT ); Fri, 5 Jan 2018 09:54:29 -0500 Message-ID: <1515164061.3305.17.camel@debian.org> Subject: Re: [PATCH 0/7] IBRS patch series From: Yves-Alexis Perez To: Paolo Bonzini , Greg KH Cc: Henrique de Moraes Holschuh , Tim Chen , Justin Forbes , Thomas Gleixner , Andy Lutomirski , Linus Torvalds , Dave Hansen , Andrea Arcangeli , Andi Kleen , Arjan Van De Ven , linux-kernel@vger.kernel.org Date: Fri, 05 Jan 2018 15:54:21 +0100 In-Reply-To: <2b40f988-e773-97a5-77ca-de0908887ae2@redhat.com> References: <2c1e7299-56ea-07ec-8077-471f17ad3c79@linux.intel.com> <1515099712.30693.22.camel@debian.org> <20180105132856.GA12036@kroah.com> <1515160065.3305.6.camel@debian.org> <20180105140145.GA24434@kroah.com> <2b40f988-e773-97a5-77ca-de0908887ae2@redhat.com> Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-AX0RtpYQWbsFYfW3X+45" X-Mailer: Evolution 3.26.3-1 Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: --=-AX0RtpYQWbsFYfW3X+45 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 2018-01-05 at 15:26 +0100, Paolo Bonzini wrote: > Those from November seem way too early to include IBRS/IBPB. Maybe the > two from December 3rd, but I wouldn't be 100% sure. So, for my CPU with updated microcode: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 61 model name : Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz stepping : 4 microcode : 0x28 cpuid returns: 0x00000007 0x00: eax=3D0x00000000 ebx=3D0x021c27ab ecx=3D0x00000000 edx=3D0x0c000000 So bit 26/27 are set, which as I understand means IBRS is supported (but I would appreciate any pointer to relevant documentation on this). >=20 > So it would be even nicer to know how those microcode updates were tested= . At least I didn't test IBRS/IBPB here. I could do it provided I'm pointed t= o a tree with all the things to test. >=20 > (And by the way, the LFENCE change is for variant 1 aka CVE-2017-5753). Ok, good to know. Is the kernel support part for LFENCE in the same thread = (I have to admit I'm a bit lost). Regards, --=20 Yves-Alexis --=-AX0RtpYQWbsFYfW3X+45 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlpPkZ0ACgkQ3rYcyPpX RFukoQf/RULKSdS9LLUyqVfgKeOJWuETGDiBVsGhFK1riwrA7AGDYWnZy273ZF0a eG/eVKfjHrCe6hy3Os7yBgCMxGFr3pdNxjYIDiTfyxwhE3EzKxNINIx1RAshzpr+ bxsK11zy7+/CX5U1VPwFodc8EO96fCJ0wXvbcm2TQtkJsA8zG2zXlcuenEVZf2eR 990BG8k5bpO4cQTt+RZKMf3lgBSAaFPOtVMyTK1TRZixUBTU+EkNeoAOnOKGEFvt CxKWJH5G4B7Jbbt1H4oxVsUonyJdjD9qVE5F9uNyMY+FT1lAfLz0pQLExcv4EXOP N0uGZ0e6cIXV/bd9RIySONKIpJlpVw== =IiyZ -----END PGP SIGNATURE----- --=-AX0RtpYQWbsFYfW3X+45--