linux-kernel - Re: [PATCH V2 0/3] xen: remove some memory limits from pv-domains

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <54199E23.7090403@citrix.com>
Date:	Wed, 17 Sep 2014 15:43:47 +0100
From:	David Vrabel <david.vrabel@...rix.com>
To:	Juergen Gross <jgross@...e.com>, <linux-kernel@...r.kernel.org>,
	<xen-devel@...ts.xensource.com>, <konrad.wilk@...cle.com>,
	<boris.ostrovsky@...cle.com>, <jbeulich@...e.com>
Subject: Re: [PATCH V2 0/3] xen: remove some memory limits from pv-domains

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.

David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/