From: Mulyadi Santosa <mulyadi.santosa@gmail.com>
To: "海峰 陈" <gg8_8@yahoo.com.cn>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] asking for your help
Date: Mon, 20 Sep 2010 07:56:18 +0700 [thread overview]
Message-ID: <AANLkTi=dXhPTdDX4oTfgdzsLgG7NNMXtdtPEaMijnhMq@mail.gmail.com> (raw)
In-Reply-To: <935244.33291.qm@web15101.mail.cnb.yahoo.com>
Hi...
I just lend a small help, hopefully it helps...
On Sun, Sep 19, 2010 at 17:56, 海峰 陈 <gg8_8@yahoo.com.cn> wrote:
>
> Dear friends,
>
> I'm a student and i will do some work about QEMU memory management mechanism. However, i am a
>
> freshman, i need friends to give me some suggestion or send some helpfull documentation to me. Thanks.
I suggest, next time, send plain ASCII email. No HTML format, no
picture embedded as background....etc, please? In this kind of
technical discussion list, they are just wasting spaces. So unless it
is useful to explain something (.eg diagram..), don't embed pictures.
OK, about qemu memory management. Have you ever read the Qemu source
code? If you haven't, please download, extract and start reading it.
The very basic fundamental of Qemu memory management is that it's
actually a file mmap()-ed into the guest address space. The size of
the this simulated RAM is a large as the size you pass at -m parameter
(by default, it's 256 MB if I remember correctly).
The start of the mmap()-ed address, is considered as offset zero in
this virtual RAM. Every access to this virtual RAM is like the same
like actual RAM e.g there is page fault, reserved memory address and
so on. It's just it's not so complicated. IIRC, there is no actual L1
or L2 cache. Probably it's due to the fact that they are simulated as
mmaped file.
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
prev parent reply other threads:[~2010-09-20 0:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-19 10:56 [Qemu-devel] asking for your help 海峰 陈
2010-09-20 0:56 ` Mulyadi Santosa [this message]
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='AANLkTi=dXhPTdDX4oTfgdzsLgG7NNMXtdtPEaMijnhMq@mail.gmail.com' \
--to=mulyadi.santosa@gmail.com \
--cc=gg8_8@yahoo.com.cn \
--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).