| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] [PATCH] x86-64: don't use xmalloc_array() for allocation
>>> On 13.10.11 at 16:44, Keir Fraser <keir.xen@xxxxxxxxx> wrote:
> On 13/10/2011 13:14, "Jan Beulich" <JBeulich@xxxxxxxx> wrote:
>
>>>>> On 13.10.11 at 11:34, Keir Fraser <keir@xxxxxxx> wrote:
>>> Given our antipathy to the x86-32 hypervisor, and the fact that any
>>> remaining users of it are unlikely to be running MP systems at all let alone
>>> large MP systems, how about this cleanup patch?... (It looks quite confusing
>>> as a patch, actually, but does the obvious thing).
>>
>> Looks good to me - I was actually considering to convert the x86-64
>> code back to alloc_xenheap_pages() too (for we'll need to do that
>> eventually anyway when we want to support more than 5Tb of memory)
>> when I put together that earlier patch, but then refrained from doing so
>> to keep the patch size down.
>
> You mean there's a 5TB limit for alloc_domheap_pages() allocations??
No, I mean that currently we can't use more than 5Tb on any system.
Due to address space limitations, going beyond that will require to
introduce split domain and Xen heaps (including map_domain_page() etc)
and hence the consistent use of alloc_xenheap_pages() vs.
alloc_domheap_pages() (which currently isn't the case - you fixed just
one group of them). Remember talking about that on the summit?
> I only switched to alloc_xenheap_pages() because it's safe for x86-32 too...
Sure, I just wanted to point out that this needs to be done at some point
anyway.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home