From: Fabrice Bellard <fabrice.bellard@free.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] powerpc hang
Date: Thu, 07 Aug 2003 10:02:37 +0200 [thread overview]
Message-ID: <3F32079D.6020306@free.fr> (raw)
In-Reply-To: 1060210228.10894.50.camel@lxws8.ad.newisys.com
The branch in JUMP_TB can jump to one of two targets:
1) The next instruction which sets 'T0' to the Translation Block (TB)
address ored with the branch index (0 or 1) and env->eip to the target
EIP value. This is the default (and slow) case.
2) Directly to the TB corresponding to the target EIP value.
The information stored in the translation block tells where to find the
'branch' instruction in the TB (16 bit offset from the start of the
translated block) and which value must be stored in it to jump to the
next instruction (another 16 bit offset).
Fabrice.
Jon Nall wrote:
> hello.
> i'm pretty new to qemu and last night set out to help debug the current
> ppc hang when using gcc3. trying to understand the code has left me with
> a question about how op_jmp_tb_next works on powerpc. would someone
> kindly walk through what should happen? i'm speficially curious about:
>
> - how the branch in JUMP_TB gets patched if T0 == 0 in cpu_exec()
> - how the tb_jmp_offset member is ultimately used
next prev parent reply other threads:[~2003-08-07 8:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 22:50 [Qemu-devel] powerpc hang Jon Nall
2003-08-07 8:02 ` Fabrice Bellard [this message]
2003-08-07 22:05 ` Jon Nall
2003-08-08 9:20 ` Christof Petig
2003-08-08 13:13 ` Jon Nall
2003-08-09 2:48 ` Jon Nall
2003-08-09 10:51 ` Fabrice Bellard
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=3F32079D.6020306@free.fr \
--to=fabrice.bellard@free.fr \
--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).