From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NNDkd-000757-2p for qemu-devel@nongnu.org; Tue, 22 Dec 2009 18:02:47 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NNDkY-00072b-Sv for qemu-devel@nongnu.org; Tue, 22 Dec 2009 18:02:46 -0500 Received: from [199.232.76.173] (port=50078 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NNDkY-00072S-Mb for qemu-devel@nongnu.org; Tue, 22 Dec 2009 18:02:42 -0500 Received: from mail2.shareable.org ([80.68.89.115]:33505) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NNDkY-0007A4-8x for qemu-devel@nongnu.org; Tue, 22 Dec 2009 18:02:42 -0500 Date: Tue, 22 Dec 2009 23:02:38 +0000 From: Jamie Lokier Subject: Re: [Qemu-devel] cpuid problem in upstream qemu with kvm Message-ID: <20091222230238.GD19806@shareable.org> References: <4B2DF334.6030208@redhat.com> <20091220155101.GB31257@redhat.com> <4B2E49E5.6050709@redhat.com> <20091220165612.GC31257@redhat.com> <20091220171822.GD31257@redhat.com> <20091220172341.GB21163@redhat.com> <2162E312-0110-42E1-A391-D75A6F013554@suse.de> <20091220173702.GC21163@redhat.com> <4B2E660F.1050703@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B2E660F.1050703@codemonkey.ws> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: qemu-devel@nongnu.org, Alexander Graf , Avi Kivity , Gleb Natapov , "Michael S. Tsirkin" Anthony Liguori wrote: > It would be insane to emulate sse3 too. It doesn't sound too ridiculous if TCG is involved, provided the switching between TCG and KVM isn't too rapid. TCG is slower, but it's not ridiculously slow. Though, I don't expect anyone to volunteer to implement it :-) > how likely is it that any given guest is using an obscure feature? Could KVM detect when a guest starts using each feature? For example, by disabling access to those features, enabling each one when the KVM trap occurs and recording that fact? Is it possible to enable them in the guest-visible cpuid, but force a trap on access to them? That might be quite useful information when you want to migrate something that wasn't planned for X years ago. -- Jamie