[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] stable format of e820map for HVM domU's ?
I'm currently getting the amount of pseudo-physical memory allocated to the current domU in hvmloader by reading the e820map. Here's a sample one for a domU w/ 128 meg: BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009f800 (usable) BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved) BIOS-e820: 00000000000a0000 - 00000000000c0000 type 16 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 0000000007ffd000 (usable) BIOS-e820: 0000000007ffd000 - 0000000007ffe000 type 19 BIOS-e820: 0000000007ffe000 - 0000000007fff000 type 18 BIOS-e820: 0000000007fff000 - 0000000008000000 type 17 BIOS-e820: 0000000008000000 - 0000000008003000 (ACPI NVS) BIOS-e820: 0000000008003000 - 000000000800d000 (ACPI data) BIOS-e820: 00000000fec00000 - 0000000100000000 type 16 What's the least likely to change way to get what I want out of here? In this case, the type 17 entry's ending address is the capacity. Can I always ignore the last 3 entries? Should I use the type 17 entry as the last pseudo-physical one? Some other way? Many thanks for your help. Andrew _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |