qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	Markus Armbruster <armbru@redhat.com>,
	kvm-devel <kvm@vger.kernel.org>,
	Mark McLoughlin <markmc@redhat.com>
Subject: Re: [Qemu-devel] Planning for the 0.11.0 release
Date: Fri, 10 Jul 2009 18:40:54 +0100	[thread overview]
Message-ID: <200907101840.55859.paul@codesourcery.com> (raw)
In-Reply-To: <4A577465.1050104@us.ibm.com>

> 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

  parent reply	other threads:[~2009-07-10 17:41 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 23:57 [Qemu-devel] Planning for the 0.11.0 release Anthony Liguori
2009-06-23 12:12 ` Avi Kivity
2009-06-23 15:09 ` Blue Swirl
2009-06-23 15:47   ` Anthony Liguori
2009-06-23 15:49   ` Avi Kivity
2009-07-09  8:27 ` Mark McLoughlin
2009-07-09 13:32   ` Anthony Liguori
2009-07-10  1:10     ` Markus Armbruster
2009-07-10 13:53       ` Anthony Liguori
2009-07-10 15:04         ` Jan Kiszka
2009-07-10 15:49           ` Anthony Liguori
2009-07-10 16:23             ` Jan Kiszka
2009-07-10 16:33               ` Anthony Liguori
2009-07-10 16:52                 ` Jan Kiszka
2009-07-10 17:03                   ` Anthony Liguori
2009-07-10 17:15                     ` Jan Kiszka
2009-07-10 17:40                     ` Paul Brook [this message]
2009-07-10 17:58                       ` Anthony Liguori
2009-07-10 18:02                       ` Jan Kiszka
2009-07-10 18:22                         ` Paul Brook
2009-07-10 16:55             ` Kevin Wolf
2009-07-10 16:59               ` Anthony Liguori
2009-07-10 17:10                 ` Kevin Wolf
2009-07-10 17:31                   ` Anthony Liguori
2009-07-10 17:10                 ` Christoph Hellwig
2009-07-10 17:12                   ` Kevin Wolf
2009-07-10 18:26                     ` Christoph Hellwig
2009-07-10 17:29                   ` Anthony Liguori
2009-07-10 18:13                     ` Christoph Hellwig
2009-07-10 18:29                       ` Anthony Liguori
2009-07-10 17:06               ` Anthony Liguori
2009-07-12  8:31                 ` Avi Kivity

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200907101840.55859.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=aliguori@us.ibm.com \
    --cc=armbru@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=markmc@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).