From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [PATCH v2 16/17] kvm: x86: Rework identity map and TSS setup for larger BIOS sizes Date: Mon, 03 Jan 2011 17:52:29 +0100 Message-ID: <4D21FECD.9000103@web.de> References: <4D21F416.9090300@redhat.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigA636BBFEE983AB4B2E418F41" Cc: Marcelo Tosatti , kvm@vger.kernel.org, qemu-devel@nongnu.org, Jan Kiszka To: Avi Kivity Return-path: Received: from fmmailgate03.web.de ([217.72.192.234]:57581 "EHLO fmmailgate03.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754320Ab1ACQwf (ORCPT ); Mon, 3 Jan 2011 11:52:35 -0500 In-Reply-To: <4D21F416.9090300@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigA636BBFEE983AB4B2E418F41 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Am 03.01.2011 17:06, Avi Kivity wrote: > On 01/03/2011 10:33 AM, Jan Kiszka wrote: >> From: Jan Kiszka >> >> First of all, we only need this EPT identity and TSS reservation on >> Intel CPUs. >=20 > kvm-amd will ignore it just fine. I'd like to keep arch differences > away from userspace. And I would prefer to avoid needlessly cluttering the physical guest address space where not needed. Long term, we could even give user space a hint (unless it can test it directly) that this workaround is no longer needed as the host Intel CPU supports true real mode. >=20 >> Then, in order to support loading BIOSes> 256K, reorder the >> code, adjusting the base if the kernel supports moving the identity ma= p. >> We can drop the check for KVM_CAP_SET_TSS_ADDR as we already depend on= >> much newer features. >=20 > There is no ordering on kvm features. Each can come and go as it pleas= es. >=20 Well, at least this is not how kvm upstream works so far. Jan --------------enigA636BBFEE983AB4B2E418F41 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.15 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk0h/s0ACgkQitSsb3rl5xTkZgCg3ZSVRlC8OZ/mb8g4aRzjuMKY fWEAoKfD/z32UC5Nhe9oJUqP+4v1ZDaz =pLlh -----END PGP SIGNATURE----- --------------enigA636BBFEE983AB4B2E418F41--