| commit | 201728429d6cf336cfd7483fcd1bce47291b2901 | |
| author | Daniel Vetter <daniel.vetter@ffwll.ch> | |
| Fri, 24 Sep 2010 16:25:59 +0000 (24 18:25 +0200) | ||
| committer | Chris Wilson <chris@chris-wilson.co.uk> | |
| Wed, 27 Oct 2010 22:31:07 +0000 (27 23:31 +0100) | ||
| tree | 162c9084104373fd587347f5b7b2e20951430d98 | treesnapshot (tar.gz zip) |
| parent | b3eafc5af02a799650757f2c5b2b0d4835dd0a5f | commitdiff |
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>
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>
| drivers/char/agp/intel-agp.h | diffblobblamehistory | |
| drivers/char/agp/intel-gtt.c | diffblobblamehistory |