search for: ro_mpt_virt_start

While adding code to create the compatibility p2m table mappings it seemed to me that the creation of the native ones is restricted to memory below the 512G boundary - otherwise, additional L2 tables would need to be allocated (currently other memory following the one L2 page getting allocated would be blindly overwritten). While I realize that machines this big aren''t likely to be

...for a domU having paging mode set to PG_translate. I see that, populate_physmap() after calling __alloc_xen_heap_pages only updates the machine_to_physmap but how is the mfn for the allocated page being updated/set for phys_to_machine_mapping?? I see that phys_to_machine_mapping is a #defined to RO_MPT_VIRT_START which inturn is defined as PML4_ADDR(256).. what is this?? i have completely lose track from here on. Thanks in advance. Regards, Sandesh Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this messag...

Populate-on-demand: Check pages being returned by the balloon driver This patch series is the second result of my work last summer on decreasing fragmentation of superpages in a guests'' p2m when using populate-on-demand. This patch series is against 4.1; I''m posting it to get feedback on the viability of getting a ported version of this patch into 4.2. As with the previous