From: Ahmed Azab <amazab@ncsu.edu>
To: xen-devel@lists.xensource.com
Subject: Xen's Code location
Date: Tue, 23 Jun 2009 11:58:48 -0400 [thread overview]
Message-ID: <4A40FBB8.8020806@ncsu.edu> (raw)
Hi all,
I was inspecting Xen trying to understand the mechanism of booting the
hypervisor and the way Xen's memory is managed inside its own address
space. I am using x86/32-bit Xen with PAE. According to the documents,
Xen should occupy the highest 168 MB of the address space (i.e. higher
than 0xf5800000). I have two questions:
1- What are the boundaries of the different sections (code, ro data,
heap, etc..) with this address space?
I searched within Xen's source but I got now clue about the location
Xen's code is mapped. I used objdump on the booted Xen kernel and is
said that there is only one section, which is .text, that should be
loaded at 0x0010000 which is not even a high address. I inspected the
function __start_xen in setup.c but it does not do any code address
relocation. Finally, I inspected Xen's GDT and I found that it used a
flat segmentation structure (4 GB per segment)
2-Is there any page protection within Xen's address space?
I noticed that all mapped pages are executable which is supposed to
include Xen's stack and heap.
Thanks,
Ahmed
reply other threads:[~2009-06-23 15:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4A40FBB8.8020806@ncsu.edu \
--to=amazab@ncsu.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.