From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KyUiO-0006JS-Ag for qemu-devel@nongnu.org; Fri, 07 Nov 2008 12:01:44 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KyUiM-0006Hn-Hp for qemu-devel@nongnu.org; Fri, 07 Nov 2008 12:01:43 -0500 Received: from [199.232.76.173] (port=43925 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KyUiM-0006HM-3J for qemu-devel@nongnu.org; Fri, 07 Nov 2008 12:01:42 -0500 Received: from mx2.redhat.com ([66.187.237.31]:48628) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KyUiL-0007Hi-Kg for qemu-devel@nongnu.org; Fri, 07 Nov 2008 12:01:41 -0500 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id mA7H1e9D001803 for ; Fri, 7 Nov 2008 12:01:40 -0500 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id mA7H1dB6012003 for ; Fri, 7 Nov 2008 12:01:40 -0500 Received: from zweiblum.travel.kraxel.org (vpn-4-83.str.redhat.com [10.32.4.83]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id mA7H1cUS005876 for ; Fri, 7 Nov 2008 12:01:39 -0500 Message-ID: <49147472.6030807@redhat.com> Date: Fri, 07 Nov 2008 18:01:38 +0100 From: Gerd Hoffmann MIME-Version: 1.0 Subject: Re: [Qemu-devel] kvm: sync registers? References: <491416EA.30706@redhat.com> <49144ABA.1030606@codemonkey.ws> <200811071631.54494.paul@codesourcery.com> In-Reply-To: <200811071631.54494.paul@codesourcery.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Paul Brook wrote: > On Friday 07 November 2008, Anthony Liguori wrote: >> Gerd Hoffmann wrote: >>> Hi, >>> >>> How does kvm sync registers between kernel and qemu env? >>> I see there are kvm_arch_{get,put}_registers() functions in >>> target-i386/kvm.c, but grep doesn't find a single call of them? >> Right now, it doesn't. We should probably sync registers in the same >> places that kvm-userspace does (gdbstubs, vmport, etc.). >> >> I tried to always sync registers on every exit but this causes boot to >> fail. The same is true of kvm-userspace though and I've been meaning to >> dig into why this is. > > Maybe due to do with inconsistencies between the segment register contents and > the descriptor tables? I know I've written code that relies on this feature. Unlikely. xenner depends on that too, and also on kvm supporting it. start-of-day actually sets up the segment registers only, not any descriptor tables, then starts the guest in protected mode.