Prev: [PATCH -v2] x86, cacheinfo: Carve out L3 cache slot accessors
Next: linux-next: Tree for June 2 (staging/comedi)
From: Bill Richardson on 2 Jun 2010 12:30
On Wed, Jun 2, 2010 at 9:14 AM, H. Peter Anvin <hpa(a)zytor.com> wrote:
>
> No! �Bloody **** hell no!

Heh. Well, that answers that.


> This was settled in 2007 -- it is the boot loaders duty to provide a memory map. �The fact that we allowed a
> hack in to let the kernel itself add additional ranges from EFI has proven to be an utter mistake, and this is
> yet another example of it.

Ah. With that hint, I've now found some of the original discussion.
Sorry I missed it before. Having dealt with EFI for some weeks now, I
can't say I find your reaction overstated.

Thanks for the quick response.

Bill
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [PATCH -v2] x86, cacheinfo: Carve out L3 cache slot accessors
Next: linux-next: Tree for June 2 (staging/comedi)