From: Wei Liu <wei.liu2@citrix.com>
To: lmingcsce <Ming.Aaron.Liu@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
wei.liu2@citrix.com
Subject: Re: Translate virtual address to physical address
Date: Sun, 1 Jan 2012 15:22:15 +0000 [thread overview]
Message-ID: <1325431335.24422.65.camel@liuw-desktop> (raw)
In-Reply-To: <92932E0E-BC3F-44CD-953E-AC3CB7D8F0A1@gmail.com>
Please don't top-posting.
On Sun, 2012-01-01 at 14:59 +0000, lmingcsce wrote:
> Thanks for your reply.
> "Establishing a new array in the tools directory" means that I declare
> a new array in /tools/libxc/xc_domain_save.c and want to pass the
> physical address of this array to the hypervisor.
> I have already tried copy_to_user and copy_to_guest and from the
> experiment, I find that there is size limit for these two functions.
What size limit? I don't quite get it. I've never seen an array large
enough to bloat whole address space.
> By the way, I also want to ask the code organization of xen. What's
> the function of stubdom directory?
stubdom is used to boost HVM performance. It is based on minios, with
qemu compiled in. It is not mandatory though.
> When the virtual machines execute, the function in tools will execute
> in the Dom0 space? Can you illustrate that for me or give me some
> specific material? I have already seen some explanation, and don't
> find the answer.
> Thanks.
Of course tools run in Dom0, they are just normal user programs.
However, every functionality requires hypervisor to do the actual job. A
normal work flow is like:
toolstack ---(syscall)--> kernel ---(hypercall)--> hypervisor
The kernel entry is /proc/xen/privcmd, whose source code is in Linux
tree drivers/xen/xenfs.
Wei.
prev parent reply other threads:[~2012-01-01 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-31 21:52 Translate virtual address to physical address lmingcsce
2012-01-01 11:51 ` Wei Liu
2012-01-01 14:59 ` lmingcsce
2012-01-01 15:22 ` Wei Liu [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=1325431335.24422.65.camel@liuw-desktop \
--to=wei.liu2@citrix.com \
--cc=Ming.Aaron.Liu@gmail.com \
--cc=xen-devel@lists.xensource.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).