[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] 32bit xen and "claim"



>>> Dan Magenheimer <dan.magenheimer@xxxxxxxxxx> 11/01/12 9:34 PM >>>
>With the plan to obsolete the x86 32-bit hypervisor at 4.3,

That's not just a plan, but reality already.

>when prototyping the "claim" hypercall/subop, can I assume
>that the CONFIG_X86 code in the hypervisor and, specifically
>any separation of the concepts of xen_heap from dom_heap,
>can be ignored?

No, you shouldn't. Once adding support for memory amounts beyond 5Tb
I expect the separation to become meaningful even for x86-64.

>Or will the ARM version of the hypervisor be requiring
>a similar separation of xen_heap vs dom_heap?
>
>If the CONFIG_X86/separation code will no longer be used,
>shall I submit a patch to delete the code in page_alloc.c
>and memory.c?  Or can you (Keir or Jan) just delete it?

Please don't.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.