From: "Michael Neubauer" <neubauer@in.tum.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Qemu memory management
Date: Thu, 29 Mar 2007 11:58:33 +0200 [thread overview]
Message-ID: <000001c771e8$cff5c3d0$14b2a8c0@michael5ee790a> (raw)
Hello,
I'm trying to learn a bit more about the Qemu SoftMMU. The following
quotation is taken from section 2.10 of the "Qemu Internals" documentation.
"To avoid flushing the translated code each time the MMU mappings change,
QEMU uses a physically indexed translation cache. It means that each TB is
indexed with its physical address."
Why does a cache like that prevent the translated code from being flushed?
If a translated code is relocated in physical memory (e. g. after a paging
swap operation) that would render the cache useless in my opinion. Maybe I'm
just mixing too many things up here since I don't really have a lot of
experience in the whole operating systems stuff. I would really appreciate
it if someone could give me a hint.
I'm sorry if that's the wrong place to ask questions like the one above.
Please let me know if there's any other comprehensive resource of
information available.
-- Michael
next reply other threads:[~2007-03-29 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-29 9:58 Michael Neubauer [this message]
2007-03-29 13:59 ` [Qemu-devel] Qemu memory management Stuart Brady
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='000001c771e8$cff5c3d0$14b2a8c0@michael5ee790a' \
--to=neubauer@in.tum.de \
--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).