We are currently running out of MTRRs with this CPU when
marking the graphics memory as write-combining. The reason
is that the graphics stolen memory was bumped to 64MiB which
changes the address space enough that the MTRRs are exhausted.
BUG=None
BRANCH=None
TEST=Built and analyzed MTRR usage. Also noted clearing upper
2GiB of memory in depthcharge does not take forever.
Change-Id: I2eb0168990a5c585605f958e1cbc9ec1a2322d1d
Signed-off-by: Aaron Durbin <adurbin@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/174653
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>
|
||
|---|---|---|
| .. | ||
| config.baskingridge | ||
| config.bayleybay | ||
| config.beltino | ||
| config.butterfly | ||
| config.emeraldlake2 | ||
| config.falco | ||
| config.link | ||
| config.lumpy | ||
| config.nyan | ||
| config.panther | ||
| config.parrot | ||
| config.parrot32 | ||
| config.parrot64 | ||
| config.peach_kirby | ||
| config.peach_pit | ||
| config.peppy | ||
| config.rambi | ||
| config.slippy | ||
| config.snow | ||
| config.stout | ||
| config.stout32 | ||
| config.stumpy | ||
| config.wtm2 | ||