linux-kernel - Re: [PATCH] reserve end-of-conventional-memory to 1MB on 32-bit v2

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: <20080304144915.GA4457@elte.hu>
Date:	Tue, 4 Mar 2008 15:49:15 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Mark McLoughlin <markmc@...hat.com>
Cc:	Alexander van Heukelum <heukelum@...lshack.com>,
	Ian Campbell <ijc@...lion.org.uk>,
	Alexander van Heukelum <heukelum@...tmail.fm>,
	"H. Peter Anvin" <hpa@...or.com>, Andi Kleen <ak@...e.de>,
	Thomas Gleixner <tglx@...utronix.de>,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] reserve end-of-conventional-memory to 1MB on 32-bit v2


* Mark McLoughlin <markmc@...hat.com> wrote:

> > This is the second attempt at a i386-version of the ebda patch. I 
> > hope that one of the Xen people will be able to check that this does 
> > not break their setups, but I think it will be fine after their 
> > patch to exclude the 0x9f000- 0x100000 area explicitly in their 
> > setup.
> 
> Confirmed that with Ian's e820 map patch and your patch, Xen DomU 
> boots fine.

hm, for now i've only got the patch below queued up for v2.6.25.

Could you check whether just the patch below ontop of -rc3-ish upstream 
solves the problem too? The EBDA patch would be a bit risky now - it's 
queued up for v2.6.26 at the moment.

	Ingo

--------------->
Subject: x86/xen: fix DomU boot problem
From: Ian Campbell <ijc@...lion.org.uk>
Date: Thu, 28 Feb 2008 23:16:49 +0000

Construct Xen guest e820 map with a hole between 640K-1M.

It's pure luck that Xen kernels have gotten away with it in the past.

The patch below seems like the right thing to do. It certainly boots in
a domU without the DMI problem (without any of the other related patches
such as Alexander's).

Signed-off-by: Ian Campbell <ijc@...lion.org.uk>
Cc: H. Peter Anvin <hpa@...or.com>
Cc: Jeremy Fitzhardinge <jeremy@...p.org>
Tested-by: Mark McLoughlin <markmc@...hat.com>
Acked-by: Mark McLoughlin <markmc@...hat.com>
Signed-off-by: Ingo Molnar <mingo@...e.hu>
---
 arch/x86/xen/setup.c |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

Index: linux-x86.q/arch/x86/xen/setup.c
===================================================================
--- linux-x86.q.orig/arch/x86/xen/setup.c
+++ linux-x86.q/arch/x86/xen/setup.c
@@ -38,7 +38,8 @@ char * __init xen_memory_setup(void)
 	unsigned long max_pfn = xen_start_info->nr_pages;
 
 	e820.nr_map = 0;
-	add_memory_region(0, PFN_PHYS(max_pfn), E820_RAM);
+	add_memory_region(0, LOWMEMSIZE(), E820_RAM);
+	add_memory_region(HIGH_MEMORY, PFN_PHYS(max_pfn)-HIGH_MEMORY, E820_RAM);
 
 	return "Xen";
 }
--
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/