Hello, all I thought dom0 is layed out on physical memory starting 0, linearly, but this message, (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1d87000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000c14000000->0000000c18000000 (498514 pages to be allocated) shows the address range 0000000c14000000->0000000c18000000 , what is this? it''s 64MB range and why 64MB from Dom0 is located here? I think 498514 pages will be allocated later, but where, exactly?? if dom0''s memory is partitioned into several places, then, what happens to their GPFN?? thanks Min
On Fri, 2013-02-01 at 00:31 +0000, Min Lee wrote:> Hello, all > I thought dom0 is layed out on physical memory starting 0, linearly, but > this message, > > (XEN) *** LOADING DOMAIN 0 *** > (XEN) Xen kernel: 64-bit, lsb, compat32 > (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1d87000 > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 0000000c14000000->0000000c18000000 (498514 pages to > be allocated) > > shows the address range 0000000c14000000->0000000c18000000 , > what is this?That is the virtual address range. The start of day memory layout is described in http://xenbits.xen.org/docs/unstable/hypercall/include,public,xen.h.html#incontents_startofday> it''s 64MB range and why 64MB from Dom0 is located here?This is the size of the initial mapping given your kenrel and initrd size etc.> I think 498514 pages will be allocated later, but where, exactly??IIRC the kernel will map it as part of its initialisation, init_memory_mapping() in Linux perhaps?> if dom0''s memory is partitioned into several places, > then, what happens to their GPFN??I''m not sure I understand this question. Ian.
Thank you for your reply, Ian. I''ll take a look at them.. thanks! Min On 2/4/2013 4:38 AM, Ian Campbell wrote:> On Fri, 2013-02-01 at 00:31 +0000, Min Lee wrote: >> Hello, all >> I thought dom0 is layed out on physical memory starting 0, linearly, but >> this message, >> >> (XEN) *** LOADING DOMAIN 0 *** >> (XEN) Xen kernel: 64-bit, lsb, compat32 >> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1d87000 >> (XEN) PHYSICAL MEMORY ARRANGEMENT: >> (XEN) Dom0 alloc.: 0000000c14000000->0000000c18000000 (498514 pages to >> be allocated) >> >> shows the address range 0000000c14000000->0000000c18000000 , >> what is this? > > That is the virtual address range. > > The start of day memory layout is described in > http://xenbits.xen.org/docs/unstable/hypercall/include,public,xen.h.html#incontents_startofday > >> it''s 64MB range and why 64MB from Dom0 is located here? > > This is the size of the initial mapping given your kenrel and initrd > size etc. > >> I think 498514 pages will be allocated later, but where, exactly?? > > IIRC the kernel will map it as part of its initialisation, > init_memory_mapping() in Linux perhaps? > >> if dom0''s memory is partitioned into several places, >> then, what happens to their GPFN?? > > I''m not sure I understand this question. > > Ian. > > >