From: Tim Deegan <tim@xen.org>
To: Baozeng <sploving1@gmail.com>
Cc: xen-devel@lists.xen.org
Subject: Re: xen dire-map area
Date: Thu, 14 Jun 2012 10:58:16 +0100 [thread overview]
Message-ID: <20120614095816.GF82539@ocelot.phlegethon.org> (raw)
In-Reply-To: <CAP=GMUHmHfeE1rDk37HcoHW5ytVHqSaTqyXHt24M9r+q6QDg=g@mail.gmail.com>
At 17:30 +0800 on 14 Jun (1339695001), Baozeng wrote:
> Hell all,
>
> I am doing some research work on protecting Xen's data structures.
> I know there is a direct-map area(about 12M), in which we can get the
> physical address of the data structure from its virtual address. My
> question is : are the stack and the heap of Xen both located in this
> direct-map area?
On 32-bit x86, anything allocated with alloc_xenheap_* or xmalloc() is
in that area (and that includes Xen's stacks). Anything allocated with
alloc_domheap_* is not. Also the frametable and M2P are mapped
separately. The details are in include/asm-x86/config.h.
Cheers,
Tim.
next prev parent reply other threads:[~2012-06-14 9:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 9:30 xen dire-map area Baozeng
2012-06-14 9:58 ` Tim Deegan [this message]
2012-06-15 7:15 ` Baozeng
2012-06-15 13:16 ` Tim Deegan
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=20120614095816.GF82539@ocelot.phlegethon.org \
--to=tim@xen.org \
--cc=sploving1@gmail.com \
--cc=xen-devel@lists.xen.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).