From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1KyUFb-0006v2-GS
	for qemu-devel@nongnu.org; Fri, 07 Nov 2008 11:31:59 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1KyUFa-0006uY-12
	for qemu-devel@nongnu.org; Fri, 07 Nov 2008 11:31:58 -0500
Received: from [199.232.76.173] (port=55935 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1KyUFZ-0006uV-RG
	for qemu-devel@nongnu.org; Fri, 07 Nov 2008 11:31:57 -0500
Received: from mail.codesourcery.com ([65.74.133.4]:60142)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <paul@codesourcery.com>) id 1KyUFZ-0007Mv-Fv
	for qemu-devel@nongnu.org; Fri, 07 Nov 2008 11:31:57 -0500
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] kvm: sync registers?
Date: Fri, 7 Nov 2008 17:31:53 +0100
References: <491416EA.30706@redhat.com> <49144ABA.1030606@codemonkey.ws>
In-Reply-To: <49144ABA.1030606@codemonkey.ws>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200811071631.54494.paul@codesourcery.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

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.

Paul