All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: David Vrabel <david.vrabel@citrix.com>,
	Juergen Gross <jgross@suse.com>, <linux-kernel@vger.kernel.org>,
	<xen-devel@lists.xensource.com>, <konrad.wilk@oracle.com>,
	<boris.ostrovsky@oracle.com>
Subject: Re: [Xen-devel] [Patch V3 14/15] xen: allow more than 512 GB of RAM for 64 bit pv-domains
Date: Wed, 27 May 2015 18:05:59 +0100	[thread overview]
Message-ID: <5565F977.102@citrix.com> (raw)
In-Reply-To: <5565EFE2.7050308@citrix.com>

On 27/05/15 17:25, David Vrabel wrote:
> On 20/04/15 06:23, Juergen Gross wrote:
>> 64 bit pv-domains under Xen are limited to 512 GB of RAM today. The
>> main reason has been the 3 level p2m tree, which was replaced by the
>> virtual mapped linear p2m list. Parallel to the p2m list which is
>> being used by the kernel itself there is a 3 level mfn tree for usage
>> by the Xen tools and eventually for crash dump analysis. For this tree
>> the linear p2m list can serve as a replacement, too. As the kernel
>> can't know whether the tools are capable of dealing with the p2m list
>> instead of the mfn tree, the limit of 512 GB can't be dropped in all
>> cases.
>>
>> This patch replaces the hard limit by a kernel parameter which tells
>> the kernel to obey the 512 GB limit or not. The default is selected by
>> a configuration parameter which specifies whether the 512 GB limit
>> should be active per default for domUs (domain save/restore/migration
>> and crash dump analysis are affected).
>>
>> Memory above the domain limit is returned to the hypervisor instead of
>> being identity mapped, which was wrong anyway.
>>
>> The kernel configuration parameter to specify the maximum size of a
>> domain can be deleted, as it is not relevant any more.
> 
> Something in this patch breaks the hvc console in my test domU.
> 
> kernel BUG at /local/davidvr/work/k.org/tip/drivers/tty/hvc/hvc_xen.c:153
> 
> Which suggests the hvc driver mapped the wrong console ring frame.

Sorry, it's patch #13 (xen: move p2m list if conflicting with e820 map)
that seems to be bad.

David

WARNING: multiple messages have this Message-ID (diff)
From: David Vrabel <david.vrabel@citrix.com>
To: David Vrabel <david.vrabel@citrix.com>,
	Juergen Gross <jgross@suse.com>,
	linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
	konrad.wilk@oracle.com, boris.ostrovsky@oracle.com
Subject: Re: [Xen-devel] [Patch V3 14/15] xen: allow more than 512 GB of RAM for 64 bit pv-domains
Date: Wed, 27 May 2015 18:05:59 +0100	[thread overview]
Message-ID: <5565F977.102@citrix.com> (raw)
In-Reply-To: <5565EFE2.7050308@citrix.com>

On 27/05/15 17:25, David Vrabel wrote:
> On 20/04/15 06:23, Juergen Gross wrote:
>> 64 bit pv-domains under Xen are limited to 512 GB of RAM today. The
>> main reason has been the 3 level p2m tree, which was replaced by the
>> virtual mapped linear p2m list. Parallel to the p2m list which is
>> being used by the kernel itself there is a 3 level mfn tree for usage
>> by the Xen tools and eventually for crash dump analysis. For this tree
>> the linear p2m list can serve as a replacement, too. As the kernel
>> can't know whether the tools are capable of dealing with the p2m list
>> instead of the mfn tree, the limit of 512 GB can't be dropped in all
>> cases.
>>
>> This patch replaces the hard limit by a kernel parameter which tells
>> the kernel to obey the 512 GB limit or not. The default is selected by
>> a configuration parameter which specifies whether the 512 GB limit
>> should be active per default for domUs (domain save/restore/migration
>> and crash dump analysis are affected).
>>
>> Memory above the domain limit is returned to the hypervisor instead of
>> being identity mapped, which was wrong anyway.
>>
>> The kernel configuration parameter to specify the maximum size of a
>> domain can be deleted, as it is not relevant any more.
> 
> Something in this patch breaks the hvc console in my test domU.
> 
> kernel BUG at /local/davidvr/work/k.org/tip/drivers/tty/hvc/hvc_xen.c:153
> 
> Which suggests the hvc driver mapped the wrong console ring frame.

Sorry, it's patch #13 (xen: move p2m list if conflicting with e820 map)
that seems to be bad.

David

  reply	other threads:[~2015-05-27 17:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20  5:23 [Patch V3 00/15] xen: support pv-domains larger than 512GB Juergen Gross
2015-04-20  5:23 ` [Patch V3 01/15] xen: sync with xen headers Juergen Gross
2015-04-20  5:23 ` [Patch V3 02/15] xen: save linear p2m list address in shared info structure Juergen Gross
2015-04-20  5:23 ` [Patch V3 03/15] xen: don't build mfn tree if tools don't need it Juergen Gross
2015-04-20  5:23 ` [Patch V3 04/15] xen: eliminate scalability issues from initial mapping setup Juergen Gross
2015-04-20  5:23 ` [Patch V3 05/15] xen: move static e820 map to global scope Juergen Gross
2015-04-20  5:23 ` [Patch V3 06/15] xen: split counting of extra memory pages from remapping Juergen Gross
2015-04-20  5:23 ` [Patch V3 07/15] xen: check memory area against e820 map Juergen Gross
2015-04-20  5:23 ` [Patch V3 08/15] xen: find unused contiguous memory area Juergen Gross
2015-04-20  5:23 ` [Patch V3 09/15] xen: check for kernel memory conflicting with memory layout Juergen Gross
2015-04-20  5:23 ` [Patch V3 10/15] xen: check pre-allocated page tables for conflict with memory map Juergen Gross
2015-04-20  5:23 ` [Patch V3 11/15] xen: check for initrd conflicting with e820 map Juergen Gross
2015-04-20  5:23 ` [Patch V3 12/15] mm: provide early_memremap_ro to establish read-only mapping Juergen Gross
2015-04-20  5:23 ` [Patch V3 13/15] xen: move p2m list if conflicting with e820 map Juergen Gross
2015-04-20  5:23 ` [Patch V3 14/15] xen: allow more than 512 GB of RAM for 64 bit pv-domains Juergen Gross
2015-05-27 16:25   ` [Xen-devel] " David Vrabel
2015-05-27 16:25     ` David Vrabel
2015-05-27 17:05     ` David Vrabel [this message]
2015-05-27 17:05       ` David Vrabel
2015-06-08  5:09       ` Juergen Gross
2015-06-08  5:09         ` Juergen Gross
2015-04-20  5:23 ` [Patch V3 15/15] xen: remove no longer needed p2m.h Juergen Gross
2015-05-19 10:11 ` [Xen-devel] [Patch V3 00/15] xen: support pv-domains larger than 512GB David Vrabel
2015-05-19 10:11   ` David Vrabel

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=5565F977.102@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jgross@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 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.