On 6/26/07, Andi Kleen <[email protected]> wrote:
RevE had a new memory remapping scheme (memory hoisting) at least, which I think you refered to earlier. There might have been more changes in F.
yes, REV E has hardware memory remapping. Rev F you don't need to use mtrr to set MEM to WE above 4G. YH - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- [PATCH] trim memory not covered by WB MTRRs
- From: Jesse Barnes <[email protected]>
- Re: [PATCH] trim memory not covered by WB MTRRs
- From: Andi Kleen <[email protected]>
- Re: [PATCH] trim memory not covered by WB MTRRs
- From: Jesse Barnes <[email protected]>
- Re: [PATCH] trim memory not covered by WB MTRRs
- From: [email protected] (Eric W. Biederman)
- Re: [PATCH] trim memory not covered by WB MTRRs
- From: Andi Kleen <[email protected]>
- Re: [PATCH] trim memory not covered by WB MTRRs
- From: [email protected] (Eric W. Biederman)
- Re: [PATCH] trim memory not covered by WB MTRRs
- From: Andi Kleen <[email protected]>
- [PATCH] trim memory not covered by WB MTRRs
- Prev by Date: Re: [2.6.22-rc6] NForce4 soft and hard resetting ports and exceptions
- Next by Date: Re: [Bug 8679] New: Section mismatch: reference to .init.text
- Previous by thread: Re: [PATCH] trim memory not covered by WB MTRRs
- Next by thread: Re: [PATCH] trim memory not covered by WB MTRRs
- Index(es):
 |