qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: 陳韋任 <chenwj@iis.sinica.edu.tw>
To: Lei Li <lilei@linux.vnet.ibm.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] TB chaining
Date: Thu, 22 Sep 2011 10:36:11 +0800	[thread overview]
Message-ID: <20110922023611.GA14886@cs.nctu.edu.tw> (raw)
In-Reply-To: <4E7A9D2E.20402@linux.vnet.ibm.com>

> 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.

  "list of TBs jumping to this one" make me think that jmp_next and
jmp_first store those TBs jump to this TB. But it seems the actual
use of jmp_next is another way around, jmp_next points to those TBs
next to this one.

Regards,
chenwj

-- 
Wei-Ren Chen (陳韋任)
Computer Systems Lab, Institute of Information Science,
Academia Sinica, Taiwan (R.O.C.)
Tel:886-2-2788-3799 #1667

  reply	other threads:[~2011-09-22  2:36 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
2011-09-22  2:36       ` 陳韋任 [this message]
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=20110922023611.GA14886@cs.nctu.edu.tw \
    --to=chenwj@iis.sinica.edu.tw \
    --cc=lilei@linux.vnet.ibm.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).