summaryrefslogtreecommitdiffstats
path: root/net
diff options
context:
space:
mode:
authorDaniel Vetter <daniel.vetter@ffwll.ch>2010-09-24 18:25:59 +0200
committerChris Wilson <chris@chris-wilson.co.uk>2010-10-27 23:31:07 +0100
commit201728429d6cf336cfd7483fcd1bce47291b2901 (patch)
tree162c9084104373fd587347f5b7b2e20951430d98 /net
parentb3eafc5af02a799650757f2c5b2b0d4835dd0a5f (diff)
downloadop-kernel-dev-201728429d6cf336cfd7483fcd1bce47291b2901.zip
op-kernel-dev-201728429d6cf336cfd7483fcd1bce47291b2901.tar.gz
intel-gtt: maximize ggtt size on platforms that support this
On VT-d supporting platforms the GGTT is allocated in a stolen mem section separate from graphcis stolen mem. The GMCH register contains a bitfield specifying the size of that region. Docs suggest that this region can only be used for GGTT and PPGTT. Hence ensure that the PPGTT is disabled and use the complete area for the GGTT. Unfortunately the graphics core on G33/Pineview can't cope with really large GTTs and the BIOS usually enables the maximum of 512MB. So don't bother with maximizing the GTT on these platforms. Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud