Xen Memory Map

From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Proper place for an overview of Xen virtual space Date: Thu, 26 Jul 2012 09:54:43 -0400 Message-ID: <20120726135443.GC28024@phenom.dumpdata.com> References: <201207261129.22383.ptesarik@suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <201207261129.22383.ptesarik@suse.cz> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Petr Tesarik Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Thu, Jul 26, 2012 at 11:29:21AM +0200, Petr Tesarik wrote: > Hello all, > > while working on makedumpfile support of Xen4, I made a side-by-side > comparison of the Xen3 and Xen4 virtual space on x86_64 (attached). I believe > that it can be useful to others as well, but I don't know what would be an > appropriate place for it. Nice! It might be also usefull to add the PGD/PUd indexes so one knows that that the M2P sits in 261 (and in 256), ioremap is 267, etc.. > > Regards, > Petr Tesarik > SUSE Linux > > > > Xen Memory Map > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >

Range	Xen3	Xen4

0x0000000000000000 0x00007fffffffffff	[128T] Guest-defined use
0x0000800000000000 0xffff7fffffffffff	[16E] Inaccessible
0xffff800000000000 0xffff803fffffffff	[256G] Read-only machine-to-phys translation table > (GUEST ACCESSIBLE)
0xffff804000000000 0xffff807fffffffff	[256G] Reserved for future shared info with the > guest OS (GUEST ACCESSIBLE)
0xffff808000000000 0xffff80ffffffffff	[512G] Reserved for future use	[512G] ioremap for PCI mmconfig space
0xffff810000000000 0xffff817fffffffff	[512G] Guest linear page table
0xffff818000000000 0xffff81ffffffffff	[512G] Shadow linear page table
0xffff820000000000 0xffff827fffffffff	[512G] Per-domain mappings (e.g., GDT, LDT)
0xffff828000000000 0xffff8283ffffffff	[16G] Machine-to-phys translation table	[256G] Machine-to-phys translation table
0xffff828400000000 0xffff8287ffffffff	[16G] Page-frame information array
0xffff828800000000 0xffff828bffffffff	[16G] ioremap()/fixmap area
0xffff828c00000000 0xffff828c3fffffff	[1G] Compatibility machine-to-phys translation table
0xffff828c40000000 0xffff828c7fffffff	[1G] High read-only compat machine-to-phys translation table
0xffff828c80000000 0xffff828cbfffffff	[1G] Xen text, static data, bss
0xffff828cc0000000 0xffff82bfffffffff	[461G] Reserved for future use
0xffff82c000000000 0xffff82c3ffffffff		[16G] ioremap()/fixmap area
0xffff82c400000000 0xffff82c43fffffff		[1G] Compatibility machine-to-phys translation table
0xffff82c440000000 0xffff82c47fffffff		[1G] High read-only compat machine-to-phys translation table
0xffff82c480000000 0xffff82c4bfffffff		[1G] Xen text, static data, bss
0xffff82c4c0000000 0xffff82f5ffffffff		[197G] Reserved for future use
0xffff82f600000000 0xffff82ffffffffff		[40G] Page-frame information array
0xffff830000000000 0xffff83ffffffffff	[1T] 1:1 direct mapping of all physical memory	[5T] 1:1 direct mapping of all physical memory
0xffff840000000000 0xffff87ffffffffff	[4T] Reserved for future use	[5T] 1:1 direct mapping of all physical memory
0xffff880000000000 0xffffffffffffffff	[120T] Guest-defined use

> > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel