[Intel-gfx] Ugly patches for stolen reservation

Jesse Barnes jbarnes at virtuousgeek.org
Fri Jul 26 04:14:52 CEST 2013


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). 

Jesse


--
Jesse Barnes, Intel Open Source Technology Center


-------- Original message --------
From: "H. Peter Anvin" <hpa at zytor.com> 
Date: 07/25/2013  5:49 PM  (GMT-08:00) 
To: Jesse Barnes <jbarnes at virtuousgeek.org> 
Cc: Ingo Molnar <mingo at kernel.org>,intel-gfx at lists.freedesktop.org,linux-kernel at vger.kernel.org,mingo at elte.hu,tglx at linutronix.de,torvalds at linux-foundation.org 
Subject: Re: Ugly patches for stolen reservation 
 
On 07/25/2013 04:17 PM, Jesse Barnes wrote:
> Well, it's ok if the boot loader writes to this memory, the worst
> that'll happen is you'll see garbage on the screen.  If the boot loader
> tries to do MMIO mapping on top it'll get into trouble... but why would
> it do that?
> 
> Jesse

Much worse: it could be hunting for a place to put the kernel, and put
it there.

-hpa



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx/attachments/20130725/c8a1797e/attachment-0001.html>


More information about the Intel-gfx mailing list