All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xen.org>
To: Jan Beulich <JBeulich@suse.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] x86-64: don't use xmalloc_array() for allocation of the (per-CPU) IDTs
Date: Thu, 13 Oct 2011 16:23:32 +0100	[thread overview]
Message-ID: <CABCC104.32A10%keir@xen.org> (raw)
In-Reply-To: <4E971D06020000780005B352@nat28.tlf.novell.com>

On 13/10/2011 16:16, "Jan Beulich" <JBeulich@suse.com> 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.

      reply	other threads:[~2011-10-13 15:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-13  7:21 [PATCH] x86-64: don't use xmalloc_array() for allocation of the (per-CPU) IDTs Jan Beulich
2011-10-13  7:50 ` Keir Fraser
2011-10-13  7:55   ` Jan Beulich
2011-10-13  8:15     ` Keir Fraser
2011-10-13 18:36       ` Konrad Rzeszutek Wilk
2011-10-13  9:34   ` Keir Fraser
2011-10-13 12:14     ` Jan Beulich
2011-10-13 14:44       ` Keir Fraser
2011-10-13 15:16         ` Jan Beulich
2011-10-13 15:23           ` 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=CABCC104.32A10%keir@xen.org \
    --to=keir@xen.org \
    --cc=JBeulich@suse.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.