From: Stuart Brady <sdbrady@ntlworld.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Add single stepping option for all targets
Date: Mon, 29 Dec 2008 14:40:04 +0000 [thread overview]
Message-ID: <20081229144004.GA12510@miranda.arrow> (raw)
In-Reply-To: <494D18B1.8080900@mail.berlios.de>
On Sat, Dec 20, 2008 at 05:09:21PM +0100, Stefan Weil wrote:
> The patch does not add single step mode for Qemu's user mode emulation.
> Would this be useful, too?
Single stepping in user mode emulation could be quite useful for the
development of any target that doesn't have system emulation yet, so
I imagine that I'll need it at some point for this very reason.
(You didn't actually say, but I would assume that the extra check for
single stepping after the translation of each instruction has a
negligable effect on performance.)
I expect that many of the existing targets are stable enough that single
stepping isn't really needed for those targets per se, but I've found
that single stepping can be very helpful when debugging host support,
and it can generally be quite annoying to have to keep rebuilding with
different #defines uncommented.
Cheers,
--
Stuart Brady
next prev parent reply other threads:[~2008-12-29 14:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-20 16:09 [Qemu-devel] [PATCH] Add single stepping option for all targets Stefan Weil
2008-12-29 12:34 ` Stefan Weil
2008-12-29 14:40 ` Stuart Brady [this message]
2009-02-01 19:51 ` Stefan Weil
2009-02-01 22:24 ` Laurent Desnogues
2009-02-04 12:50 ` Stefan Weil
2009-02-28 16:27 ` Stefan Weil
2009-03-01 20:52 ` Aurelien Jarno
2009-03-03 6:38 ` Aurelien Jarno
2009-03-13 16:35 ` Stefan Weil
2009-03-13 16:54 ` Laurent Desnogues
2009-03-13 17:21 ` [Qemu-devel] " Jan Kiszka
2009-03-20 15:42 ` [Qemu-devel] " Stefan Weil
2009-03-28 22:12 ` Aurelien Jarno
2009-03-30 10:18 ` Stefan Weil
2009-04-05 20:09 ` Aurelien Jarno
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=20081229144004.GA12510@miranda.arrow \
--to=sdbrady@ntlworld.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).