Xen Memory Map

From mboxrd@z Thu Jan 1 00:00:00 1970 From: Petr Tesarik Subject: Proper place for an overview of Xen virtual space Date: Thu, 26 Jul 2012 11:29:21 +0200 Message-ID: <201207261129.22383.ptesarik@suse.cz> Mime-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_y3QEQlIaUiRpGpI" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --Boundary-00=_y3QEQlIaUiRpGpI Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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. Regards, Petr Tesarik SUSE Linux --Boundary-00=_y3QEQlIaUiRpGpI Content-Type: text/html; charset="us-ascii"; name="xen-memmap.html" Content-Transfer-Encoding: 7bit Content-Description: Xen Virtual Memory Map Content-Disposition: attachment; filename="xen-memmap.html" 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

--Boundary-00=_y3QEQlIaUiRpGpI Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --Boundary-00=_y3QEQlIaUiRpGpI-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: Proper place for an overview of Xen virtual space Date: Thu, 26 Jul 2012 14:53:33 +0100 Message-ID: <1343310813.6812.34.camel@zakaz.uk.xensource.com> References: <201207261129.22383.ptesarik@suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: 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, 2012-07-26 at 10:29 +0100, 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. Somewhere on the wiki perhaps? BTW I don't think Xen3 and Xen4 are the right labels, perhaps 3.4 and 4.0? The 3->4 major number change was only a number change, it didn't signal a rearchitecting or anything like that (other than the normal development between a release). Labelling it Xen3 and Xen4 suggests it did. 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: Proper place for an overview of Xen virtual space Date: Thu, 26 Jul 2012 15:08:53 +0100 Message-ID: References: <201207261129.22383.ptesarik@suse.cz> <1343310813.6812.34.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1343310813.6812.34.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: "xen-devel@lists.xensource.com" , Petr Tesarik List-Id: xen-devel@lists.xenproject.org On Thu, Jul 26, 2012 at 2:53 PM, Ian Campbell wrote: > On Thu, 2012-07-26 at 10:29 +0100, 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. > > Somewhere on the wiki perhaps? The comparison would probably go on the wiki somewhere. Do we have a layout for memory in the documentation directory in-tree? If not, that might be useful. But it should be only the current memory layout, I think; a comparison is best suited to a wiki. -George From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: Proper place for an overview of Xen virtual space Date: Thu, 26 Jul 2012 15:10:26 +0100 Message-ID: <1343311826.6812.35.camel@zakaz.uk.xensource.com> References: <201207261129.22383.ptesarik@suse.cz> <1343310813.6812.34.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: George Dunlap Cc: "xen-devel@lists.xensource.com" , Petr Tesarik List-Id: xen-devel@lists.xenproject.org On Thu, 2012-07-26 at 15:08 +0100, George Dunlap wrote: > On Thu, Jul 26, 2012 at 2:53 PM, Ian Campbell wrote: > > On Thu, 2012-07-26 at 10:29 +0100, 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. > > > > Somewhere on the wiki perhaps? > > The comparison would probably go on the wiki somewhere. Do we have a > layout for memory in the documentation directory in-tree? If not, > that might be useful. But it should be only the current memory > layout, I think; a comparison is best suited to a wiki. There's comments in xen/include/asm-*/config.h with the layout. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Petr Tesarik Subject: Re: Proper place for an overview of Xen virtual space Date: Fri, 27 Jul 2012 07:41:47 +0200 Message-ID: <201207270741.47235.ptesarik@suse.cz> References: <201207261129.22383.ptesarik@suse.cz> <1343310813.6812.34.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Return-path: In-Reply-To: <1343310813.6812.34.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org RG5lIMSMdCAyNi4gxI1lcnZlbmNlIDIwMTIgMTU6NTM6MzMgSWFuIENhbXBiZWxsIG5hcHNhbChh KToKPiBPbiBUaHUsIDIwMTItMDctMjYgYXQgMTA6MjkgKzAxMDAsIFBldHIgVGVzYXJpayB3cm90 ZToKPiA+IEhlbGxvIGFsbCwKPiA+IAo+ID4gd2hpbGUgd29ya2luZyBvbiBtYWtlZHVtcGZpbGUg c3VwcG9ydCBvZiBYZW40LCBJIG1hZGUgYSBzaWRlLWJ5LXNpZGUKPiA+IGNvbXBhcmlzb24gb2Yg dGhlIFhlbjMgYW5kIFhlbjQgdmlydHVhbCBzcGFjZSBvbiB4ODZfNjQgKGF0dGFjaGVkKS4gSQo+ ID4gYmVsaWV2ZSB0aGF0IGl0IGNhbiBiZSB1c2VmdWwgdG8gb3RoZXJzIGFzIHdlbGwsIGJ1dCBJ IGRvbid0IGtub3cgd2hhdAo+ID4gd291bGQgYmUgYW4gYXBwcm9wcmlhdGUgcGxhY2UgZm9yIGl0 Lgo+IAo+IFNvbWV3aGVyZSBvbiB0aGUgd2lraSBwZXJoYXBzPwoKU3VyZSwgSSBjYW4gYWRkIGEg cGFnZSB0aGVyZSwgYnV0IG5vYm9keSB3aWxsIGZpbmQgaXQgdW5sZXNzIEkgbGluayBpdCBmcm9t IApzb21ld2hlcmUsIGJ1dCBJJ20gdW5hYmxlIHRvIGZpbmQgYSBnb29kIHBsYWNlIGZvciB0aGUg bGluay4KCj4gQlRXIEkgZG9uJ3QgdGhpbmsgWGVuMyBhbmQgWGVuNCBhcmUgdGhlIHJpZ2h0IGxh YmVscywgcGVyaGFwcyAzLjQgYW5kCj4gNC4wPyBUaGUgMy0+NCBtYWpvciBudW1iZXIgY2hhbmdl IHdhcyBvbmx5IGEgbnVtYmVyIGNoYW5nZSwgaXQgZGlkbid0Cj4gc2lnbmFsIGEgcmVhcmNoaXRl Y3Rpbmcgb3IgYW55dGhpbmcgbGlrZSB0aGF0IChvdGhlciB0aGFuIHRoZSBub3JtYWwKPiBkZXZl bG9wbWVudCBiZXR3ZWVuIGEgcmVsZWFzZSkuIExhYmVsbGluZyBpdCBYZW4zIGFuZCBYZW40IHN1 Z2dlc3RzIGl0Cj4gZGlkLgoKQW5kIHVudGlsIG5vdyBJJ3ZlIHRob3VnaCB0aGlzIHdhcyBpbmRl ZWQgdGhlIGNhc2UuIEF0IGxlYXN0IG1hbnkgaW50ZXJuYWwgCnN0cnVjdHVyZXMgdXNlZCBieSB0 aGUga2R1bXAgaW5mcmFzdHJ1Y3R1cmUgaGF2ZSBjaGFuZ2VkIHN1YnN0YW50aWFsbHkgYmV0d2Vl biAKMy40IGFuZCA0LjAsIHdoaWxlIHRoZXkgcmVtYWluZWQgdGhlIHNhbWUgYXQgbGVhc3QgZnJv bSAzLjAuMiB0byAzLjQuCgpBbnl3YXksIHdoeSB3YXNuJ3QgNC4wIGxhYmVsbGVkIDMuNSBpZiB0 aGVyZSB3YXMgbm8gYmlnIGNoYW5nZT8KClBldHIgVGVzYXJpawpTVVNFIExpbnV4CgpfX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpYZW4tZGV2ZWwgbWFpbGlu ZyBsaXN0Clhlbi1kZXZlbEBsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi1k ZXZlbAo= From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: Proper place for an overview of Xen virtual space Date: Fri, 27 Jul 2012 08:15:30 +0100 Message-ID: <50125C320200007800090DE5@nat28.tlf.novell.com> References: <201207261129.22383.ptesarik@suse.cz> <1343310813.6812.34.camel@zakaz.uk.xensource.com> <201207270741.47235.ptesarik@suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <201207270741.47235.ptesarik@suse.cz> Content-Disposition: inline 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" , Ian Campbell List-Id: xen-devel@lists.xenproject.org >>> On 27.07.12 at 07:41, Petr Tesarik wrote: > Anyway, why wasn't 4.0 labelled 3.5 if there was no big change? It was until pretty late in the release process. Iirc during late 3.4 the transition to 4.0 was already done and then reverted. All of this more for marketing/PR purposes than for technical reasons (much like Linux'es 2.6.x -> 3.x transition). Jan From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: Proper place for an overview of Xen virtual space Date: Fri, 27 Jul 2012 11:02:54 +0100 Message-ID: <1343383374.6812.139.camel@zakaz.uk.xensource.com> References: <201207261129.22383.ptesarik@suse.cz> <1343310813.6812.34.camel@zakaz.uk.xensource.com> <201207270741.47235.ptesarik@suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Return-path: In-Reply-To: <201207270741.47235.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 T24gRnJpLCAyMDEyLTA3LTI3IGF0IDA2OjQxICswMTAwLCBQZXRyIFRlc2FyaWsgd3JvdGU6Cj4g RG5lIMSMdCAyNi4gxI1lcnZlbmNlIDIwMTIgMTU6NTM6MzMgSWFuIENhbXBiZWxsIG5hcHNhbChh KToKPiA+IE9uIFRodSwgMjAxMi0wNy0yNiBhdCAxMDoyOSArMDEwMCwgUGV0ciBUZXNhcmlrIHdy b3RlOgo+ID4gPiBIZWxsbyBhbGwsCj4gPiA+IAo+ID4gPiB3aGlsZSB3b3JraW5nIG9uIG1ha2Vk dW1wZmlsZSBzdXBwb3J0IG9mIFhlbjQsIEkgbWFkZSBhIHNpZGUtYnktc2lkZQo+ID4gPiBjb21w YXJpc29uIG9mIHRoZSBYZW4zIGFuZCBYZW40IHZpcnR1YWwgc3BhY2Ugb24geDg2XzY0IChhdHRh Y2hlZCkuIEkKPiA+ID4gYmVsaWV2ZSB0aGF0IGl0IGNhbiBiZSB1c2VmdWwgdG8gb3RoZXJzIGFz IHdlbGwsIGJ1dCBJIGRvbid0IGtub3cgd2hhdAo+ID4gPiB3b3VsZCBiZSBhbiBhcHByb3ByaWF0 ZSBwbGFjZSBmb3IgaXQuCj4gPiAKPiA+IFNvbWV3aGVyZSBvbiB0aGUgd2lraSBwZXJoYXBzPwo+ IAo+IFN1cmUsIEkgY2FuIGFkZCBhIHBhZ2UgdGhlcmUsIGJ1dCBub2JvZHkgd2lsbCBmaW5kIGl0 IHVubGVzcyBJIGxpbmsgaXQgZnJvbSAKPiBzb21ld2hlcmUsIGJ1dCBJJ20gdW5hYmxlIHRvIGZp bmQgYSBnb29kIHBsYWNlIGZvciB0aGUgbGluay4KCkl0IHdpbGwgYXQgbGVhc3QgbWVhbiBJIGNh biBhbnN3ZXIgdGhlIHF1ZXN0aW9uICJob3cgaGFzIHRoZSBtZW1vcnkgbWFwCmNoYW5nZWQiIHdp dGggYSBsaW5rIGluc3RlYWQgb2YgYW4gYWN0dWFsIGV4cGxhbmF0aW9uLCBhbmQgb25jZSBhIGZl dwpwZW9wbGUgaGF2ZSBhc2tlZCBpdCdsbCBzdGFydCB0byBzaG93IHVwIG9uIGdvb2dsZSBldGMg ZHVlIHRvIHRoZSBsaW5rcwppbiB0aGUgTUwgYXJjaGl2ZXMgYW5kIHNvIG9uLgoKWW91IHNob3Vs ZCBhbHNvIGVuc3VyZSB0byBhZGQgaXQgdG8gdGhlIHByb3BlciBjYXRlZ29yaWVzIG9uIHRoZSB3 aWtpIHNvCnRoYXQgcGVvcGxlIHNlYXJjaGluZyB0aGUgd2lraSBjYW4gZmluZCBpdC4KCj4gQW55 d2F5LCB3aHkgd2Fzbid0IDQuMCBsYWJlbGxlZCAzLjUgaWYgdGhlcmUgd2FzIG5vIGJpZyBjaGFu Z2U/CgpJdCdzIGp1c3QgYSBudW1iZXIgYW5kIHBlb3BsZSBmZWx0IGxpa2UgaXQgd2FzIHRpbWUu IExpa2UgdGhlIExpbnV4CjIuNi54LT4zLnggdHJhbnNpdGlvbi4KCklhbi4KCgpfX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpYZW4tZGV2ZWwgbWFpbGluZyBs aXN0Clhlbi1kZXZlbEBsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi1kZXZl bAo=