From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] Planning for the 0.11.0 release
Date: Fri, 10 Jul 2009 18:40:54 +0100
Message-ID: <200907101840.55859.paul@codesourcery.com>
References: <4A401A65.3080804@us.ibm.com> <4A5771C3.7050103@siemens.com> <4A577465.1050104@us.ibm.com>
Mime-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	Mark McLoughlin <markmc@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	"kvm-devel" <kvm@vger.kernel.org>
To: qemu-devel@nongnu.org
Return-path: <kvm-owner@vger.kernel.org>
Received: from mail.codesourcery.com ([65.74.133.4]:51159 "EHLO
	mail.codesourcery.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751033AbZGJRk7 (ORCPT <rfc822;kvm@vger.kernel.org>);
	Fri, 10 Jul 2009 13:40:59 -0400
In-Reply-To: <4A577465.1050104@us.ibm.com>
Content-Disposition: inline
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

> Right, that part I'm okay with.  But the vCont based gdb model presumes
> a unified address space which while usually true for kernel address
> spaces, isn't universally true and certainly not true when PC is in
> userspace.  That's what I understood to be the major objection to vCont.

The thread bits are the wrong way to do things, but are probably relatively 
harmless for now. Expect me to remove them at the first available opportunity.

The 32/64-bit switching is just plain wrong, and makes it absolutely 
impossible for a client debugger to work correctly.
If you really can't be bothered fixing gdb (and you *really* should), then it 
should be some form of user switch that tells qemu to always report a 32-bit 
register set.

Paul