Re: [PATCH] x86: split e820 reserved entries record to late

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Linus Torvalds <torvalds@...>
Cc: Yinghai Lu <yhlu.kernel@...>, Ingo Molnar <mingo@...>, Thomas Gleixner <tglx@...>, Andrew Morton <akpm@...>, Jesse Barnes <jbarnes@...>, <linux-kernel@...>
Date: Thursday, August 28, 2008 - 4:29 pm

Linus Torvalds wrote:

My thinking is that if we run into a region which is reserved in e820 
but points to a real BAR, we would want to keep that BAR pinned, since a 
legitimate BIOS might use this mechanism to indicate that the device 
implemented by that BAR is used by SMM or ACPI.  If not, in most cases 
we will only have wasted some address space.  The sucky case, of course, 
would be an uninitialized BAR pointing into unusable address space which 
happens to be reserved in e820.  This seems very difficult to 
disambiguate from the above case through any algorithm that I can think of.


I suspect that for any possible behaviour, there will be at least one 
system out there doing something broken for it :(

	-hpa
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [PATCH] x86: split e820 reserved entries record to late, H. Peter Anvin, (Thu Aug 28, 4:29 pm)