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

Re: [Xen-devel] [PATCH 00/11] x86: support up to 16Tb


  • To: Jan Beulich <JBeulich@xxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxx>
  • Date: Wed, 23 Jan 2013 10:16:35 +0000
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxx>
  • Delivery-date: Wed, 23 Jan 2013 10:17:05 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>
  • Thread-index: Ac35Urj/Yv8N9ku1mk2MB2AjTNn6og==
  • Thread-topic: [Xen-devel] [PATCH 00/11] x86: support up to 16Tb

On 23/01/2013 09:56, "Jan Beulich" <JBeulich@xxxxxxxx> wrote:

>>>> On 23.01.13 at 10:33, Keir Fraser <keir@xxxxxxx> wrote:
>> There's an 'ifdef PAGE_LIST_NULL' in patch 11 in x86/setup.c. Is that really
>> needed?
> 
> That's there so that once we go beyond 16Tb the code won't need
> to change. In particular, because of the implied growth of struct
> page_info, I'm envisioning such support to become optional (to be
> enabled at build time).

Defer the ifdef until it's needed, then when it's added its in the sensible
place (ie. where PAGE_LIST_NULL really does become build-time optional).

 -- Keir

> 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®.