From: Keir Fraser <keir@xen.org>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH 00/11] x86: support up to 16Tb
Date: Wed, 23 Jan 2013 10:16:35 +0000 [thread overview]
Message-ID: <CD256903.59788%keir@xen.org> (raw)
In-Reply-To: <50FFC1E102000078000B89AA@nat28.tlf.novell.com>
On 23/01/2013 09:56, "Jan Beulich" <JBeulich@suse.com> wrote:
>>>> On 23.01.13 at 10:33, Keir Fraser <keir@xen.org> 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
>
prev parent reply other threads:[~2013-01-23 10:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 10:45 [PATCH 00/11] x86: support up to 16Tb Jan Beulich
2013-01-22 10:50 ` [PATCH 02/11] x86: extend frame table virtual space Jan Beulich
2013-01-22 10:50 ` [PATCH 03/11] x86: re-introduce map_domain_page() et al Jan Beulich
2013-01-22 10:51 ` [PATCH 04/11] x86: properly use map_domain_page() when building Dom0 Jan Beulich
2013-01-22 10:52 ` [PATCH 05/11] x86: consolidate initialization of PV guest L4 page tables Jan Beulich
2013-01-22 10:53 ` [PATCH 06/11] x86: properly use map_domain_page() during domain creation/destruction Jan Beulich
2013-01-22 10:55 ` [PATCH 07/11] x86: properly use map_domain_page() during page table manipulation Jan Beulich
2013-01-22 10:55 ` [PATCH 08/11] x86: properly use map_domain_page() in nested HVM code Jan Beulich
2013-01-22 10:56 ` [PATCH 09/11] x86: properly use map_domain_page() in miscellaneous places Jan Beulich
2013-01-22 10:57 ` [PATCH 10/11] tmem: partial adjustments for x86 16Tb support Jan Beulich
2013-01-22 17:55 ` Dan Magenheimer
2013-01-22 10:57 ` [PATCH 11/11] x86: support up to 16Tb Jan Beulich
2013-01-22 15:20 ` Dan Magenheimer
2013-01-22 15:31 ` Jan Beulich
2013-01-22 10:58 ` [PATCH 12/11] x86: debugging code for testing 16Tb support on smaller memory systems Jan Beulich
2013-01-23 14:26 ` [PATCH v2] " Jan Beulich
2013-01-23 15:18 ` Keir Fraser
2013-01-24 11:36 ` Tim Deegan
2013-01-24 12:23 ` Jan Beulich
2013-01-24 12:36 ` Tim Deegan
2013-01-22 20:13 ` [PATCH 00/11] x86: support up to 16Tb Keir Fraser
2013-01-23 9:33 ` Keir Fraser
2013-01-23 9:56 ` Jan Beulich
2013-01-23 10:16 ` Keir Fraser [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CD256903.59788%keir@xen.org \
--to=keir@xen.org \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).