From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org, amateur <tianlei.zhao@gmail.com>
Subject: Re: [Qemu-devel] TB Chaining NOT Reset on TLB Flush??
Date: Sat, 16 Jun 2007 14:27:05 +0100 [thread overview]
Message-ID: <200706161427.06630.paul@codesourcery.com> (raw)
In-Reply-To: <20070616132206.GA7968@163.com>
> I read from the Qemu internal documentation this:
> ``When MMU mappings change, only the chaining of the basic
> blocks is reset (i.e. a basic block can no longer jump directly
> to another one).''
>
> But when I read the code, I find that tlb_flush() doesn't reset the
> chaining between TBs. Is that the intended behaviour?? Won't that
> cause problems on guest context switch??
The internals documentation is out of date. TBs are only chained directly when
both source and destination are on the same page.
Paul
next prev parent reply other threads:[~2007-06-16 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-16 13:22 [Qemu-devel] TB Chaining NOT Reset on TLB Flush?? amateur
2007-06-16 13:27 ` Paul Brook [this message]
2007-06-17 3:11 ` amateur
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=200706161427.06630.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=tianlei.zhao@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).