On Fri, Dec 12, 2014 at 09:20:49AM +, Chris Wilson wrote:
> On Fri, Dec 12, 2014 at 11:09:15AM +0200, Ville Syrjälä wrote:
> > On Thu, Dec 11, 2014 at 08:17:00AM +, Chris Wilson wrote:
> > > In order to act as a full command barrier by itself, we need to tell the
> > > pipecontrol to actual
On Fri, Dec 12, 2014 at 09:20:49AM +, Chris Wilson wrote:
> On Fri, Dec 12, 2014 at 11:09:15AM +0200, Ville Syrjälä wrote:
> > On Thu, Dec 11, 2014 at 08:17:00AM +, Chris Wilson wrote:
> > > In order to act as a full command barrier by itself, we need to tell the
> > > pipecontrol to actual
On Fri, Dec 12, 2014 at 11:09:15AM +0200, Ville Syrjälä wrote:
> On Thu, Dec 11, 2014 at 08:17:00AM +, Chris Wilson wrote:
> > In order to act as a full command barrier by itself, we need to tell the
> > pipecontrol to actually stall the command streamer while the flush runs.
> > We require the
On Thu, Dec 11, 2014 at 08:17:00AM +, Chris Wilson wrote:
> In order to act as a full command barrier by itself, we need to tell the
> pipecontrol to actually stall the command streamer while the flush runs.
> We require the full command barrier before operations like
> MI_SET_CONTEXT, which cu
In order to act as a full command barrier by itself, we need to tell the
pipecontrol to actually stall the command streamer while the flush runs.
We require the full command barrier before operations like
MI_SET_CONTEXT, which currently rely on a prior invalidate flush.
References: https://bugs.fr
