xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: David Vrabel <david.vrabel@citrix.com>,
	linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
	konrad.wilk@oracle.com, boris.ostrovsky@oracle.com,
	jbeulich@suse.com
Subject: Re: [PATCH V2 0/3] xen: remove some memory limits from pv-domains
Date: Wed, 17 Sep 2014 16:48:09 +0200	[thread overview]
Message-ID: <54199F29.1050507@suse.com> (raw)
In-Reply-To: <54199E23.7090403@citrix.com>

On 09/17/2014 04:43 PM, David Vrabel wrote:
> On 17/09/14 05:12, Juergen Gross wrote:
>> When a Xen pv-domain is booted the initial memory map contains multiple
>> objects in the top 2 GB including the initrd and the p2m list. This
>> limits the supported maximum size of the initrd and the maximum
>> memory size the p2m list can span is limited to about 500 GB.
>>
>> Xen however supports loading the initrd without mapping it and the
>> initial p2m list can be mapped by Xen to an arbitrary selected virtual
>> address. The following patches activate those options and thus remove
>> the limitations.
>>
>> It should be noted that the p2m list limitation isn't only affecting
>> the amount of memory a pv domain can use, but it also hinders Dom0 to
>> be started on physical systems with larger memory without reducing it's
>> memory via a Xen boot parameter. By mapping the initial p2m list to
>> an area not in the top 2 GB it is now possible to boot Dom0 on such
>> systems.
>>
>> It would be desirable to be able to use more than 512 GB in a pv
>> domain, but this would require a reorganization of the p2m tree built
>> by the kernel at boot time. As this reorganization would affect the
>> Xen tools and kexec, too, it is not included in this patch set. This
>> topic can be addressed later.
>>
>> Juergen Gross (3):
>>    xen: sync some headers with xen tree
>>    xen: eliminate scalability issues from initrd handling
>
> I've applied these two to devel/for-linus-3.18.
>
> Thanks.

Thanks, too. :-)


Juergen

      reply	other threads:[~2014-09-17 14:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-17  4:12 [PATCH V2 0/3] xen: remove some memory limits from pv-domains Juergen Gross
2014-09-17  4:12 ` [PATCH V2 1/3] xen: sync some headers with xen tree Juergen Gross
2014-09-17  4:12 ` [PATCH V2 2/3] xen: eliminate scalability issues from initrd handling Juergen Gross
2014-09-17 13:45   ` [Xen-devel] " David Vrabel
2014-09-17 14:01     ` Juergen Gross
2014-09-17  4:12 ` [PATCH V2 3/3] xen: eliminate scalability issues from initial mapping setup Juergen Gross
2014-09-17 14:07   ` [Xen-devel] " David Vrabel
2014-09-17 14:17     ` Jan Beulich
2014-09-17 14:20     ` [Xen-devel] " Juergen Gross
2014-09-17 14:42       ` David Vrabel
2014-09-17 14:47         ` Juergen Gross
2014-09-17 14:43 ` [PATCH V2 0/3] xen: remove some memory limits from pv-domains David Vrabel
2014-09-17 14:48   ` Juergen Gross [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=54199F29.1050507@suse.com \
    --to=jgross@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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).