Re: Ugly patches for stolen reservation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxx>
Date: 07/25/2013 5:49 PM (GMT-08:00)
To: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>
Cc: Ingo Molnar <mingo@xxxxxxxxxx>,intel-gfx@xxxxxxxxxxxxxxxxxxxxx,linux-kernel@xxxxxxxxxxxxxxx,mingo@xxxxxxx,tglx@xxxxxxxxxxxxx,torvalds@xxxxxxxxxxxxxxxxxxxx
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



_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

[Index of Archives]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux