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@web.de>
Subject: Re: [Qemu-devel] Re: [RESEND][PATCH] gdbstub: Add vCont support
Date: Fri, 16 Jan 2009 00:15:44 +0000	[thread overview]
Message-ID: <200901160015.44729.paul@codesourcery.com> (raw)
In-Reply-To: <496FAA5D.3000403@web.de>

>  a) Modeling cpus as processes buys us nothing compared to threads given
>     the fact that we cannot provide a stable memory mapping to the gdb
>     frontend anyway. (*)

I disagree. The process model fits perfectly. The whole point is that each CPU 
has its own virtual address space. Separate address spaces is the fundamental 
difference between a process and a thread.

If you have a multicore system where several cores share a MMU[1] then 
modelling these as threads probably make sense.

Don't confuse this with OS awareness in GDB (i.e. implementing a userspace 
debug environment via a bare metal kernel level debug interface). That's a 
completely separate issue.

>  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.

Paul

[1] or have no MMU at all.

  reply	other threads:[~2009-01-16  0:15 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 [this message]
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
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=200901160015.44729.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --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 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).