From: Lei Li <lilei@linux.vnet.ibm.com>
To: 陳韋任 <chenwj@iis.sinica.edu.tw>
Cc: qemu-devel <qemu-devel@nongnu.org>, Xin Tong <xerox.time.tech@gmail.com>
Subject: Re: [Qemu-devel] TB chaining
Date: Thu, 22 Sep 2011 10:27:58 +0800 [thread overview]
Message-ID: <4E7A9D2E.20402@linux.vnet.ibm.com> (raw)
In-Reply-To: <20110922015833.GA11618@cs.nctu.edu.tw>
On 09/22/2011 09:58 AM, 陳韋任 wrote:
>> /* 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;
> After tracing the code, I found the comment might be wrong.
> For example, if we link tb1 to tb2, i.e., tb1 -> tb2. Then
> "tb1->jmp_next[n] = tb2" and "tb2->jmp_first = tb1" (roughly
> speaking). I'm not sure if I misunderstand the comment "list
> of TBs jumping to this one", or it is just wrong.
Well, the comment is from source code. I don't catch why you think "list
of TBS jumping to this one" is wrong.
My understand is that TB chain be used forreduce switch from the translation
cache to the guest code. It will be a circular list if there is no interrupt
or exceptional.
At mean while, it's just the date related to TB chain in TB struct, it's
not about process of how TB chain work.
> Regards,
> chenwj
>
--
Lei
next prev parent reply other threads:[~2011-09-22 2:28 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
2011-09-22 1:58 ` 陳韋任
2011-09-22 2:27 ` Lei Li [this message]
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=4E7A9D2E.20402@linux.vnet.ibm.com \
--to=lilei@linux.vnet.ibm.com \
--cc=chenwj@iis.sinica.edu.tw \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.