From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:56508) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RwCId-0006KC-0E for qemu-devel@nongnu.org; Sat, 11 Feb 2012 07:43:31 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RwCIb-0002xp-Pw for qemu-devel@nongnu.org; Sat, 11 Feb 2012 07:43:30 -0500 Received: from fmmailgate02.web.de ([217.72.192.227]:45072) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RwCIb-0002xT-9K for qemu-devel@nongnu.org; Sat, 11 Feb 2012 07:43:29 -0500 Received: from moweb002.kundenserver.de (moweb002.kundenserver.de [172.19.20.108]) by fmmailgate02.web.de (Postfix) with ESMTP id 6AA561C0FC7CE for ; Sat, 11 Feb 2012 13:43:26 +0100 (CET) Message-ID: <4F36626D.7020109@web.de> Date: Sat, 11 Feb 2012 13:43:25 +0100 From: Jan Kiszka MIME-Version: 1.0 References: <4F363DB2.3080908@web.de> <4F3655E7.3090905@suse.de> In-Reply-To: <4F3655E7.3090905@suse.de> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig619DFD3466A330D1030E2C39" Subject: Re: [Qemu-devel] [PATCH v2 1/8] kvm: Set cpu_single_env only once List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= Cc: Anthony Liguori , kvm@vger.kernel.org, Gleb Natapov , Marcelo Tosatti , qemu-devel , Blue Swirl , Avi Kivity This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig619DFD3466A330D1030E2C39 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 2012-02-11 12:49, Andreas F=C3=A4rber wrote: > Am 11.02.2012 12:25, schrieb Blue Swirl: >> I think using cpu_single_env is an indication of a problem, like poor >> code, layering violation or poor API (vmport). What is your use case? >=20 > I couldn't spot any in this series. Jan, note that any new use of env o= r > cpu_single_env will need to be redone when we convert to QOM CPU. cpu_single_env should have nothing to do with QOM. The ABIs of vmport and the KVM VAPI require a reference to the calling VCPU, and that's why you find tons of them in patch 5. Jan --------------enig619DFD3466A330D1030E2C39 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/ iEUEARECAAYFAk82Ym0ACgkQitSsb3rl5xQYmQCYnxEWdyLtUofd1BzfNxVxPx9n UQCfXSzYYlcfR95Mhmp08D3RFqW51A4= =Jd8c -----END PGP SIGNATURE----- --------------enig619DFD3466A330D1030E2C39--