From: Daniel Jacobowitz <drow@false.org>
To: qemu-devel@nongnu.org
Cc: Jan Kiszka <jan.kiszka@web.de>
Subject: Re: [Qemu-devel] Re: [RESEND][PATCH] gdbstub: Add vCont support
Date: Fri, 16 Jan 2009 15:42:10 -0500 [thread overview]
Message-ID: <20090116204210.GA10315@caradoc.them.org> (raw)
In-Reply-To: <200901160015.44729.paul@codesourcery.com>
On Fri, Jan 16, 2009 at 12:15:44AM +0000, Paul Brook wrote:
> > b) The model is already part of mainline qemu. This patch is just
> > about adding even more usefulness to it.
>
> I have no problems with ripping out the bogus "thread" support once (or even
> before) proper process support is implemented. Likewise I've no problem
> requiring a recent GDB if you want to do multicore debugging.
This is a bit of a different case than the x86 32-bit / 64-bit
problem. The hack is contained entirely in the qemu implementation
and once we have a GDB that supports process model - or specifically
a multi-core model - it should be easy to adapt qemu. In the mean
time, I don't see a problem with Jan's patch; it's how hardware
debuggers generally present cores to GDB at the present time.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-01-16 20:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 14:44 [Qemu-devel] [RESEND][PATCH] gdbstub: Add vCont support Jan Kiszka
2009-01-14 15:03 ` Krumme, Chris
2009-01-14 16:30 ` [Qemu-devel] " Jan Kiszka
2009-01-15 20:32 ` [Qemu-devel] " Anthony Liguori
2009-01-15 21:27 ` [Qemu-devel] " Jan Kiszka
2009-01-16 0:15 ` Paul Brook
2009-01-16 8:05 ` Jan Kiszka
2009-01-16 8:38 ` Jan Kiszka
2009-01-16 17:05 ` Paul Brook
2009-01-16 19:25 ` Jan Kiszka
2009-01-16 20:42 ` Daniel Jacobowitz [this message]
2009-01-17 10:03 ` Jamie Lokier
2009-01-17 17:33 ` Paul Brook
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=20090116204210.GA10315@caradoc.them.org \
--to=drow@false.org \
--cc=jan.kiszka@web.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.