From: Lei Li <lilei@linux.vnet.ibm.com>
To: Xin Tong <xerox.time.tech@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] TB chaining
Date: Thu, 22 Sep 2011 09:37:23 +0800 [thread overview]
Message-ID: <4E7A9153.9030905@linux.vnet.ibm.com> (raw)
In-Reply-To: <CALKntY0kWES6fFn2_xVN9LGgbjtyZQ3wNSvP3gV7S93n-iVk1Q@mail.gmail.com>
On 09/22/2011 07:05 AM, Xin Tong wrote:
> I am new to QEMU, can anyone please tell me where the TB chaining code is in QEMU ?
Actually, TB chaining was implemented via TB list. You might want to look at Exec.c
In struct TranslationBlock, the following data are used to directly call another TB from
the code of this one.
uint16_t tb_next_offset[2]; /* offset of original jump target */
#ifdef USE_DIRECT_JUMP
uint16_t tb_jmp_offset[2]; /* offset of jump instruction */
#else
unsigned long tb_next[2]; /* address of jump generated code */
#endif
/* list of TBs jumping to this one. This is a circular list using
the two least significant bits of the pointers to tell what is
the next pointer: 0 = jmp_next[0], 1 = jmp_next[1], 2 =
jmp_first */
struct TranslationBlock *jmp_next[2];
struct TranslationBlock *jmp_first; are used to directly call another TB from
the code of this one
> Thanks
> Xin
--
Lei
next prev parent reply other threads:[~2011-09-22 1:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 23:05 [Qemu-devel] TB chaining Xin Tong
2011-09-22 1:37 ` Lei Li [this message]
2011-09-22 1:58 ` 陳韋任
2011-09-22 2:27 ` Lei Li
2011-09-22 2:36 ` 陳韋任
2011-09-22 12:41 ` Xin Tong
2011-09-23 2:14 ` 陳韋任
[not found] ` <CALKntY2XeOc1LUE0NGXy_CKUer9+gxQykYC5hDzJnskx+OfdCQ@mail.gmail.com>
2011-09-24 2:50 ` 陳韋任
2011-09-24 10:36 ` Xin Tong
2011-09-24 11:16 ` 陳韋任
2011-11-25 1:54 ` Xin Tong
2011-11-25 2:52 ` 陳韋任
2011-09-22 2:15 ` 陳韋任
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=4E7A9153.9030905@linux.vnet.ibm.com \
--to=lilei@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=xerox.time.tech@gmail.com \
/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).