nv50: allocate an extra code bo to avoid dmesg spam
authorIlia Mirkin <imirkin@alum.mit.edu>
Mon, 13 Jan 2014 18:36:28 +0000 (13:36 -0500)
committerMaarten Lankhorst <maarten.lankhorst@canonical.com>
Mon, 27 Jan 2014 15:40:43 +0000 (16:40 +0100)
commitd98b85b50713c12e1970da08220f124b26feaab0
tree1218d4968350de74576f53c3dcc7692d0b02b463
parent58589f6c6d02f6a8b2fe4a049779129064faf2c0
nv50: allocate an extra code bo to avoid dmesg spam

Each code BO is a heap that allocates at the end first, and so GPs are
allocated at the very end of the allocated space. When executing, we see
PAGE_NOT_PRESENT errors for the next page. Just over-allocate to make
sure that there's something there.

Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu>
src/gallium/drivers/nouveau/nv50/nv50_screen.c