All of lore.kernel.org
 help / color / mirror / Atom feed
From: 陳韋任 <chenwj@iis.sinica.edu.tw>
To: Xin Tong <xerox.time.tech@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] TB chaining
Date: Sat, 24 Sep 2011 10:50:26 +0800	[thread overview]
Message-ID: <20110924025026.GA55686@cs.nctu.edu.tw> (raw)
In-Reply-To: <CALKntY2XeOc1LUE0NGXy_CKUer9+gxQykYC5hDzJnskx+OfdCQ@mail.gmail.com>

> I see, so they (jmp_next, jmp_first) are just for finding the tbs when
> unchaining is needed. do they have any other uses? also, does QEMU do inline
> caching ( when it is a conditional branch)?

  Yes, they are used for unchaining. Please see cpu_unlink_tb ->
tb_reset_jump_recursive.

  What "inline caching" means? When it's a conditional branch, the
branch target is fixed, and here comes the direct block chaining.
There is another dynamic translation technique called IBTC (indirect
branch translation cache) for indirect branch which has no fixed
branch target. But QEMU doesn't has IBTC. Could you please explain
what "inline caching" is?

Regards,
chenwj

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

  parent reply	other threads:[~2011-09-24  2:50 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       ` 陳韋任
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               ` 陳韋任 [this message]
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=20110924025026.GA55686@cs.nctu.edu.tw \
    --to=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.