From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: Why some test suite in kvm-unit-tests designed for 64bit only? Date: Fri, 31 May 2013 13:29:39 +0900 Message-ID: <51A82733.30705@web.de> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2LBSCSVASQKPQGJXLCNIJ" Cc: qemu-devel@nongnu.org, kvm , pbonzini@redhat.com To: =?UTF-8?B?IuadjuaYpeWlhyA8QXJ0aHVyIENodW5xaSBMaT4i?= Return-path: Received: from mout.web.de ([212.227.15.3]:62169 "EHLO mout.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750788Ab3EaE36 (ORCPT ); Fri, 31 May 2013 00:29:58 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2LBSCSVASQKPQGJXLCNIJ Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 2013-05-30 19:58, =E6=9D=8E=E6=98=A5=E5=A5=87 wrote= : > Hi there, > I'm now reading codes of kvm-unit-tests and I found that some of the > test cases for x86 is only designed for x86_64 (including access.flat, > apic.flat, emulator.flat, idt_test.flat and so on). I wonder why these > cases are not designed for i386? Or is there any other concerns? First of all, 32-bit hosts are rarely used in x86 virtualization today. Also, some tests may actually stress the same logic of KVM if run on 32-bit x86. That said, if you find cases where you think a 32-bit variant of a test case makes sense, feel free to suggest it! Jan ------enig2LBSCSVASQKPQGJXLCNIJ 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.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlGoJzMACgkQitSsb3rl5xSoswCgtyXJ7tzQZSmf3KI4MUvBGUxg l8YAn34sBLN/m7nfwodCPxMe7as3NYP9 =Xwti -----END PGP SIGNATURE----- ------enig2LBSCSVASQKPQGJXLCNIJ-- From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54390) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UiGyX-0008TO-6R for qemu-devel@nongnu.org; Fri, 31 May 2013 00:30:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UiGyS-0007ZG-IS for qemu-devel@nongnu.org; Fri, 31 May 2013 00:30:01 -0400 Received: from mout.web.de ([212.227.15.3]:65184) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UiGyS-0007Yu-A1 for qemu-devel@nongnu.org; Fri, 31 May 2013 00:29:56 -0400 Message-ID: <51A82733.30705@web.de> Date: Fri, 31 May 2013 13:29:39 +0900 From: Jan Kiszka MIME-Version: 1.0 References: In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2LBSCSVASQKPQGJXLCNIJ" Subject: Re: [Qemu-devel] Why some test suite in kvm-unit-tests designed for 64bit only? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?UTF-8?B?IuadjuaYpeWlhyA8QXJ0aHVyIENodW5xaSBMaT4i?= Cc: pbonzini@redhat.com, qemu-devel@nongnu.org, kvm This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2LBSCSVASQKPQGJXLCNIJ Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 2013-05-30 19:58, =E6=9D=8E=E6=98=A5=E5=A5=87 wrote= : > Hi there, > I'm now reading codes of kvm-unit-tests and I found that some of the > test cases for x86 is only designed for x86_64 (including access.flat, > apic.flat, emulator.flat, idt_test.flat and so on). I wonder why these > cases are not designed for i386? Or is there any other concerns? First of all, 32-bit hosts are rarely used in x86 virtualization today. Also, some tests may actually stress the same logic of KVM if run on 32-bit x86. That said, if you find cases where you think a 32-bit variant of a test case makes sense, feel free to suggest it! Jan ------enig2LBSCSVASQKPQGJXLCNIJ 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.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlGoJzMACgkQitSsb3rl5xSoswCgtyXJ7tzQZSmf3KI4MUvBGUxg l8YAn34sBLN/m7nfwodCPxMe7as3NYP9 =Xwti -----END PGP SIGNATURE----- ------enig2LBSCSVASQKPQGJXLCNIJ--