qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ye Wen <wen@umail.ucsb.edu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Question about softmmu
Date: Fri,  5 Nov 2004 21:22:18 -0800	[thread overview]
Message-ID: <1099718538.418c5f8acea12@webaccess.umail.ucsb.edu> (raw)

Hi, Guys:

I'm reading the QEMU code. I have a question haunting my mind for some time
about tb flushing due to MMU change. Generally, whenever the page table has
any change, we should flush the tb hash table. But I only see in the code that
when CR3 is changed, the tb_flush is called. What if the CR3 does not change,
but some level 2 page table in the memory change, should the tb also be flushed?

Thanks,

--
Ye Wen
wen@umail.ucsb.edu

             reply	other threads:[~2004-11-06  5:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-06  5:22 Ye Wen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-11-07  0:51 [Qemu-devel] Question about softmmu olivier cozette
2004-11-07  7:15 Blue Swirl

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=1099718538.418c5f8acea12@webaccess.umail.ucsb.edu \
    --to=wen@umail.ucsb.edu \
    --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).