<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body ><div>To clarify: it'll either be marked reserved or not listed at all in e820, which is why I did this early, before any other e820 stuff like the "RAM buffer" are allocated, and before we could use the iomem resource (or maybe we could even early per Linus? I'll check). </div><div><br></div><div>Jesse</div><div><br></div><div><br></div>--<div>Jesse Barnes, Intel Open Source Technology Center</div> <br><br><br>-------- Original message --------<br>From: "H. Peter Anvin" <hpa@zytor.com> <br>Date: 07/25/2013 5:49 PM (GMT-08:00) <br>To: Jesse Barnes <jbarnes@virtuousgeek.org> <br>Cc: Ingo Molnar <mingo@kernel.org>,intel-gfx@lists.freedesktop.org,linux-kernel@vger.kernel.org,mingo@elte.hu,tglx@linutronix.de,torvalds@linux-foundation.org <br>Subject: Re: Ugly patches for stolen reservation <br> <br><br>On 07/25/2013 04:17 PM, Jesse Barnes wrote:<br>> Well, it's ok if the boot loader writes to this memory, the worst<br>> that'll happen is you'll see garbage on the screen. If the boot loader<br>> tries to do MMIO mapping on top it'll get into trouble... but why would<br>> it do that?<br>> <br>> Jesse<br><br>Much worse: it could be hunting for a place to put the kernel, and put<br>it there.<br><br> -hpa<br><br><br><br></body>