From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Petr Tesarik <ptesarik@suse.cz>
Cc: xen-devel@lists.xensource.com
Subject: Re: Proper place for an overview of Xen virtual space
Date: Thu, 26 Jul 2012 09:54:43 -0400 [thread overview]
Message-ID: <20120726135443.GC28024@phenom.dumpdata.com> (raw)
In-Reply-To: <201207261129.22383.ptesarik@suse.cz>
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
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> <html>
> <head>
> <title>Xen Memory Map</title>
> <style type="text/css">
> body { color: black; background-color: white; }
> td { padding: 4px; }
> th { padding: 4px; }
> tr { vertical-align: top; }
> td.hrule { height:1px; padding: 0px; margin: 0px; background-color: black; }
> td.addr { font-family: monospace; padding-right: 16px; }
> td.code { background-color: #000080; color: white; }
> td.compat { background-color: #800000; color: white; }
> td.direct { background-color: #ffff00; }
> td.frametable { background-color: #008080; color: white; }
> td.guest { }
> td.ioremap { background-color: #008000; color: white; }
> td.mpt { background-color: #00ff00; }
> td.pagetable { }
> td.perdomain { }
> td.reserved { background-color: #c0c0c0; }
> td.unavail { background-color: #808080; color: white; }
> </style>
> </head>
> <body>
> <table>
> <thead>
> <tr><th>Range</th> <th>Xen3</th> <th>Xen4</th></tr>
> <tr><td class=hrule colspan=3></td></tr>
> </thead>
> <tbody>
> <tr>
> <td class=addr>0x0000000000000000<br>0x00007fffffffffff</td>
> <td class=guest colspan=2>[128T] Guest-defined use</td>
> </tr>
> <tr>
> <td class=addr>0x0000800000000000<br>0xffff7fffffffffff</td>
> <td class=unavail colspan=2>[16E] Inaccessible</td>
> </tr>
> <tr>
> <td class=addr>0xffff800000000000<br>0xffff803fffffffff</td>
> <td class=guest colspan=2>[256G] Read-only machine-to-phys translation table
> (GUEST ACCESSIBLE)</td>
> </tr>
> <tr>
> <td class=addr>0xffff804000000000<br>0xffff807fffffffff</td>
> <td class=reserved colspan=2>[256G] Reserved for future shared info with the
> guest OS (GUEST ACCESSIBLE)</td>
> </tr>
> <tr>
> <td class=addr>0xffff808000000000<br>0xffff80ffffffffff</td>
> <td class=reserved>[512G] Reserved for future use</td>
> <td class=ioremap>[512G] ioremap for PCI mmconfig space</td>
> </tr>
> <tr>
> <td class=addr>0xffff810000000000<br>0xffff817fffffffff</td>
> <td class=pagetable colspan=2>[512G] Guest linear page table</td>
> </tr>
> <tr>
> <td class=addr>0xffff818000000000<br>0xffff81ffffffffff</td>
> <td class=pagetable colspan=2>[512G] Shadow linear page table</td>
> </tr>
> <tr>
> <td class=addr>0xffff820000000000<br>0xffff827fffffffff</td>
> <td class=perdomain colspan=2>[512G] Per-domain mappings (e.g., GDT, LDT)</td>
> </tr>
> <tr>
> <td class=addr>0xffff828000000000<br>0xffff8283ffffffff</td>
> <td class=mpt>[16G] Machine-to-phys translation table</td>
> <td class=mpt rowspan=7>[256G] Machine-to-phys translation table</td>
> </tr>
> <tr>
> <td class=addr>0xffff828400000000<br>0xffff8287ffffffff</td>
> <td class=frametable>[16G] Page-frame information array</td>
> </tr>
> <tr>
> <td class=addr>0xffff828800000000<br>0xffff828bffffffff</td>
> <td class=ioremap>[16G] ioremap()/fixmap area</td>
> </tr>
> <tr>
> <td class=addr>0xffff828c00000000<br>0xffff828c3fffffff</td>
> <td class=compat>[1G] Compatibility machine-to-phys translation table</td>
> </tr>
> <tr>
> <td class=addr>0xffff828c40000000<br>0xffff828c7fffffff</td>
> <td class=compat>[1G] High read-only compat machine-to-phys translation table</td>
> </tr>
> <tr>
> <td class=addr>0xffff828c80000000<br>0xffff828cbfffffff</td>
> <td class=code>[1G] Xen text, static data, bss</td>
> </tr>
> <tr>
> <td class=addr>0xffff828cc0000000<br>0xffff82bfffffffff</td>
> <td class=reserved rowspan=7>[461G] Reserved for future use</td>
> </tr>
> <tr>
> <td class=addr>0xffff82c000000000<br>0xffff82c3ffffffff</td>
> <td class=ioremap>[16G] ioremap()/fixmap area</td>
> </tr>
> <tr>
> <td class=addr>0xffff82c400000000<br>0xffff82c43fffffff</td>
> <td class=compat>[1G] Compatibility machine-to-phys translation table</td>
> </tr>
> <tr>
> <td class=addr>0xffff82c440000000<br>0xffff82c47fffffff</td>
> <td class=compat>[1G] High read-only compat machine-to-phys translation table</td>
> </tr>
> <tr>
> <td class=addr>0xffff82c480000000<br>0xffff82c4bfffffff</td>
> <td class=code>[1G] Xen text, static data, bss</td>
> </tr>
> <tr>
> <td class=addr>0xffff82c4c0000000<br>0xffff82f5ffffffff</td>
> <td class=reserved>[197G] Reserved for future use</td>
> </tr>
> <tr>
> <td class=addr>0xffff82f600000000<br>0xffff82ffffffffff</td>
> <td class=frametable>[40G] Page-frame information array</td>
> </tr>
> <tr>
> <td class=addr>0xffff830000000000<br>0xffff83ffffffffff</td>
> <td class=direct>[1T] 1:1 direct mapping of all physical memory</td>
> <td class=direct rowspan=2>[5T] 1:1 direct mapping of all physical memory</td>
> </tr>
> <tr>
> <td class=addr>0xffff840000000000<br>0xffff87ffffffffff</td>
> <td class=reserved>[4T] Reserved for future use</td>
> </tr>
> <tr>
> <td class=addr>0xffff880000000000<br>0xffffffffffffffff</td>
> <td class=guest colspan=2>[120T] Guest-defined use</td>
> </tr>
> </tbody>
> </table>
> </body>
> </html>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
prev parent reply other threads:[~2012-07-26 13:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 9:29 Proper place for an overview of Xen virtual space Petr Tesarik
2012-07-26 13:53 ` Ian Campbell
2012-07-26 14:08 ` George Dunlap
2012-07-26 14:10 ` Ian Campbell
2012-07-27 5:41 ` Petr Tesarik
2012-07-27 7:15 ` Jan Beulich
2012-07-27 10:02 ` Ian Campbell
2012-07-26 13:54 ` Konrad Rzeszutek Wilk [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=20120726135443.GC28024@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=ptesarik@suse.cz \
--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.