From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MmnnN-0004AH-2N for qemu-devel@nongnu.org; Sun, 13 Sep 2009 08:03:05 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MmnnI-00044u-KX for qemu-devel@nongnu.org; Sun, 13 Sep 2009 08:03:04 -0400 Received: from [199.232.76.173] (port=49462 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MmnnI-00044l-Ek for qemu-devel@nongnu.org; Sun, 13 Sep 2009 08:03:00 -0400 Received: from fmmailgate03.web.de ([217.72.192.234]:46765) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MmnnH-00034S-PR for qemu-devel@nongnu.org; Sun, 13 Sep 2009 08:03:00 -0400 Message-ID: <4AACDF6A.9000000@web.de> Date: Sun, 13 Sep 2009 14:02:50 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <20090913081951.GO22885@redhat.com> <4AACD8A9.8090201@web.de> <20090913115039.GP22885@redhat.com> In-Reply-To: <20090913115039.GP22885@redhat.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigF96427682A1E9C4A7749DDB3" Sender: jan.kiszka@web.de Subject: [Qemu-devel] Re: [PATCH] set correct CS seg limit and flags on sipi List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gleb Natapov Cc: qemu-devel@nongnu.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF96427682A1E9C4A7749DDB3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Gleb Natapov wrote: > On Sun, Sep 13, 2009 at 01:34:01PM +0200, Jan Kiszka wrote: >> Gleb Natapov wrote: >>> TCG works with incorrect values somehow. >> TCG doesn't care about limits and has only few segment type checks. > I already noticed that TCG implement some non existent CPU somewhat > similar to x86. I once posted a patch that added full limit/flags check on memory access. But it required more work and slowed down TCG quite noticeably. Meanwhile we are only using KVM and don't require this precision anymore, so this effort stalled. >=20 >> Some link to the corresponding spec section would be nice-to-have in >> this commit message. I was looking for a reference what registers SIPI= s >> actually modify and how, but there seems to be none, at least in the >> System Programming Guide. >> > This commit just fix obvious bug that caused SIPI to put garbage into > segment's flags. I don't have link to spec only common sense. I don't disagree. I was just wondering if it loads the specified reset values into the flags or just keeps them untouched. BTW, looks like BOCHS takes your path too (ie. don't touch them). Jan --------------enigF96427682A1E9C4A7749DDB3 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.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkqs328ACgkQniDOoMHTA+kqBACbB3SPmuF5B2y2Rt6sz/6H6JXl LmQAn2i6vVsPAXE250hI3SvrpHIbBzcl =CB70 -----END PGP SIGNATURE----- --------------enigF96427682A1E9C4A7749DDB3--