Oscar Mateo <oscar.mateo@xxxxxxxxx> writes: > On 05/02/2017 09:17 AM, Mika Kuoppala wrote: >> Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> writes: >> >>> On Fri, Apr 28, 2017 at 09:11:06AM +0000, Oscar Mateo wrote: >>>> The new batchbuffer for CNL surpasses the 4096 byte mark. >>>> >>>> Cc: Mika Kuoppala <mika.kuoppala@xxxxxxxxx> >>>> Cc: Ben Widawsky <ben@xxxxxxxxxxxx> >>>> Signed-off-by: Oscar Mateo <oscar.mateo@xxxxxxxxx> >>> Evil, 4k+ of nothing-ness that userspace then has to configure for itself >>> for correctness anyway. >>> >>> Patch looks ok, but still question the sanity. >> Is there a requirement for CNL to init the renderstate? >> >> I would like to drop the render state init from CNL if >> we can't find evidence that it needs it. Bspec indicates >> that it doesnt. >> >> -Mika > > Hi Mika, > > I can double-check with the hardware architects, but word around here is > that render state init has never stopped being a requirement. Where did > you see in the BSpec that it is not required for CNL? > It would be great if you could refresh the answer and perhaps even get some answers to the 'why' parts. In the "Context Descriptor Format" section, it says: "Render CS Only: Render state need not be initialized; the Render Context Restore Inhibit bit in the Context/Save image in memory should be set to prevent restoring garbage render context." -Mika _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
