qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Problems with MIPS full system emulation and breakpoints
Date: Fri, 20 Apr 2007 14:22:09 -0400	[thread overview]
Message-ID: <20070420182209.GA18563@caradoc.them.org> (raw)
In-Reply-To: <4629005B.7030301@windriver.com>

On Fri, Apr 20, 2007 at 01:03:07PM -0500, Jason Wessel wrote:
> At this point the program is trashed on the second time through the loop 
> because the translated block with the breakpoint op code was executed instead 
> of being flushed and translated with the correct original
> instruction.

I have an idea.  When I was talking to Paul about breakpoints
recently, I noticed something very strange in the ARM port: it
continues to disassemble the instruction under a breakpoint after
generating the debug op.  This is a waste of CPU and memory, so I
tried taking it out - but he told me that if I did that, things would
go wrong because the size of the tb would be too small.  We'd try to
flush the tb at the breakpoint location, but it wouldn't seem to cover
there.

MIPS doesn't do that extra disassembly because it has a goto instead
of a break from the nested loop.  What happens if you add an extra +1
to the translation block size if there's a breakpoint, in target-mips/translate.c?

-- 
Daniel Jacobowitz
CodeSourcery

  reply	other threads:[~2007-04-20 18:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-20 18:03 [Qemu-devel] Problems with MIPS full system emulation and breakpoints Jason Wessel
2007-04-20 18:22 ` Daniel Jacobowitz [this message]
2007-09-10 15:34   ` Daniel Jacobowitz
2007-09-11 10:03     ` Thiemo Seufer
2007-05-03 20:28 ` [Qemu-devel] Problems with MIPS full system emulation and breakpoints: also for FPU emulation Stefan Weil

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=20070420182209.GA18563@caradoc.them.org \
    --to=drow@false.org \
    --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).