This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] x86-64's paging_init()

>>> Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> 31.08.06 19:58 >>>
>Correct. I suggest either a clean BUG_ON() in virt_to_xen_l2e(), or
>allocate-and-map the new l2 in that same function (but raises question of
>how to test the new code path).

Why in virt_to_xen_l2e()? We likely wouldn't make it there on a system
this big, due to earlier memory corruption.
But anyway, I'll try to change the code so the code path won't be entirely
unused (similar to the dom0 page table setup in contruct_dom0()).


>On 31/8/06 10:34 am, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:
>> 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 targeted by Xen at this point anyway (although
>> the
>> direct map area explicitly provides for 1T), I'd still want this fixed
>> if
>> someone confirms I'm not mis-reading something here (of if that's the
>> case,
>> then I'd still need a good explanation, as then I'm likely screwing up
>> the
>> compatibility table creation).

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>