From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: kvm's vapic Date: Sun, 29 Jan 2012 16:55:30 +0100 Message-ID: <4F256BF2.1010906@web.de> References: <4F2567AE.8000509@web.de> <4F256AF2.1090106@redhat.com> <4F256B4D.4080501@redhat.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigD16DC0CC7FF8447AB9C333E1" Cc: Marcelo Tosatti , Gleb Natapov , kvm To: Avi Kivity Return-path: Received: from fmmailgate02.web.de ([217.72.192.227]:34894 "EHLO fmmailgate02.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752660Ab2A2Pzd (ORCPT ); Sun, 29 Jan 2012 10:55:33 -0500 Received: from moweb001.kundenserver.de (moweb001.kundenserver.de [172.19.20.114]) by fmmailgate02.web.de (Postfix) with ESMTP id 0F3711C087FB2 for ; Sun, 29 Jan 2012 16:55:32 +0100 (CET) In-Reply-To: <4F256B4D.4080501@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigD16DC0CC7FF8447AB9C333E1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2012-01-29 16:52, Avi Kivity wrote: > On 01/29/2012 05:51 PM, Avi Kivity wrote: >>> Already the assumption that we find a CPU index at >>> fs:0x51 is apparently hard-coding this. Or that kernel code is at >>> 0x8xxxxxxx or 0xExxxxxxx. >>> >>> But what makes sure that we aren't patching some other obscure OS tha= t >>> doesn't comply with our assumptions but triggers the TPR access repor= ts >>> nevertheless?=20 >> >> Not much, but we've never had an issue. >=20 > Checking that the bios is mapped at 0x[8e]0000000 + phys should filter > out most non-Windows OSes. Possibly. What about that major/minor version entries in the KPCR? Do they work, and do we have a list of what should be there? Jan --------------enigD16DC0CC7FF8447AB9C333E1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8la/IACgkQitSsb3rl5xRBYACfSgIsgPrga7rZC0xZgHCWDu5e mZQAnAzwjS6odX239eN2NBnqFPqFrpiR =nL/h -----END PGP SIGNATURE----- --------------enigD16DC0CC7FF8447AB9C333E1--