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

Re: [Xen-devel] [PATCH] x86-64: don't use xmalloc_array() for allocation of the (per-CPU) IDTs


  • To: Jan Beulich <JBeulich@xxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxx>
  • Date: Thu, 13 Oct 2011 16:23:32 +0100
  • Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 13 Oct 2011 08:24:25 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcyJvBEPgsgYIqgogkmMRikE5V3jnA==
  • Thread-topic: [Xen-devel] [PATCH] x86-64: don't use xmalloc_array() for allocation of the (per-CPU) IDTs

On 13/10/2011 16:16, "Jan Beulich" <JBeulich@xxxxxxxx> wrote:

>>> 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?

Ah yes, I do remember now!

 K.



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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