On Mon, Mar 24, 2014 at 06:06:00PM -0700, Ben Widawsky wrote:
When PPGTT was disabled by default, the patch also prevented the user
from overriding this behavior via module parameter. Being able to test
this on arbitrary kernels is extremely beneficial to track down the
remaining bugs. The
On Tue, Mar 25, 2014 at 10:46:12AM +0100, Daniel Vetter wrote:
On Mon, Mar 24, 2014 at 06:06:00PM -0700, Ben Widawsky wrote:
When PPGTT was disabled by default, the patch also prevented the user
from overriding this behavior via module parameter. Being able to test
this on arbitrary kernels
On Tue, Mar 25, 2014 at 5:42 PM, Ben Widawsky b...@bwidawsk.net wrote:
My apologies for breaking this a bit harder than intended, and thanks for
fixing it up. Patch merged to dinq.
-Daniel
No harm, no foul. FWIW QA had been reported 0 PPGTT regressions for the
last week or so. Score one for
When PPGTT was disabled by default, the patch also prevented the user
from overriding this behavior via module parameter. Being able to test
this on arbitrary kernels is extremely beneficial to track down the
remaining bugs. The patch that prevented this was:
commit
