From: Jan Kiszka <jan.kiszka@siemens.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org, ananaza@iki.fi
Subject: [Qemu-devel] Re: [PATCH] fix gdbstub support for multiple threads in usermode, v2
Date: Wed, 17 Jun 2009 18:39:04 +0200 [thread overview]
Message-ID: <4A391C28.2010603@siemens.com> (raw)
In-Reply-To: <200906162025.54533.paul@codesourcery.com>
Paul Brook wrote:
> On Tuesday 16 June 2009, Antti P Miettinen wrote:
>> Paul Brook <paul@codesourcery.com> writes:
>>> Using threads for CPU emulation is just plain wrong.
>>>
>> Could you elaborate a bit? I've sort of assumed that to get reasonable
>> performance out of emulating a parallel target on a parallel host,
>
> You have taken this comment out of context.
>
> Exposing multiple CPUs as threads to GDB is incorrect. Each CPU has its own
> MMU (i.e. address space), so they should be exposed as processes, not threads.
Exposing them as processes isn't fitting either. As stated by Daniel, we
need a "multicore" model (or however we may call it) for gdb.
Until someone "finds" the resources to work on this, qemu's current
approach to expose VCPUs as threads is a pragmatic workaround that
covers many use cases completely and even quite a few more when you deal
with the restrictions properly.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2009-06-17 16:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 19:53 [Qemu-devel] [PATCH] fix gdbstub support for multiple threads in usermode, v2 Nathan Froyd
2009-06-02 20:08 ` Paul Brook
2009-06-02 20:46 ` Daniel Jacobowitz
2009-06-02 20:54 ` Nathan Froyd
2009-06-02 21:14 ` Paul Brook
2009-06-02 21:48 ` Nathan Froyd
2009-06-02 21:56 ` Paul Brook
2009-06-16 19:11 ` [Qemu-devel] " Antti P Miettinen
2009-06-16 19:25 ` Paul Brook
2009-06-16 20:02 ` Antti P Miettinen
2009-06-17 16:39 ` Jan Kiszka [this message]
2009-06-02 22:44 ` Jan Kiszka
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=4A391C28.2010603@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=ananaza@iki.fi \
--cc=paul@codesourcery.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).