linux-kernel - Re: [Xen-devel] [PATCH] arch/x86/xen/setup: Fix for incorrect xen_extra_mem_start initialization ifdef CONFIG_X86

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]

Date:	Thu, 12 May 2011 14:58:08 -0400
From:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To:	Daniel Kiper <dkiper@...-space.pl>
Cc:	stefano.stabellini@...citrix.com, linux-kernel@...r.kernel.org,
	xen-devel@...ts.xensource.com
Subject: Re: [Xen-devel] [PATCH] arch/x86/xen/setup: Fix for incorrect
 xen_extra_mem_start initialization ifdef CONFIG_X86_32

On Wed, May 11, 2011 at 10:34:38PM +0200, Daniel Kiper wrote:
> git commit 24bdb0b62cc82120924762ae6bc85afc8c3f2b26 (xen: do not create
> the extra e820 region at an addr lower than 4G) does not take into
> account that ifdef CONFIG_X86_32 instead of e820_end_of_low_ram_pfn()
> find_low_pfn_range() is called (both calls are from arch/x86/kernel/setup.c).
> find_low_pfn_range() behaves correctly and does not require change in
> xen_extra_mem_start initialization. Additionally, if xen_extra_mem_start
> is initialized in the same way as ifdef CONFIG_X86_64 then memory hotplug
> support for Xen balloon driver (under development) is broken.

in linux-next.
--
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/