On Sat, Jul 8, 2017 at 12:18 PM, Matt Turner wrote:
> On Sat, Jul 8, 2017 at 11:05 AM, Jason Ekstrand
> wrote:
> > On July 7, 2017 1:52:54 PM Chris Wilson
> wrote:
> >
> >> Quoting Jason Ekstrand (2017-07-07 21:37:29)
> >>>
> >>> The reason we were doing this was to ensure that the kernel did t
On Sat, Jul 8, 2017 at 11:05 AM, Jason Ekstrand wrote:
> On July 7, 2017 1:52:54 PM Chris Wilson wrote:
>
>> Quoting Jason Ekstrand (2017-07-07 21:37:29)
>>>
>>> The reason we were doing this was to ensure that the kernel did the
>>> appropriate cross-ring synchronization and flushing. However,
On July 7, 2017 1:52:54 PM Chris Wilson wrote:
Quoting Jason Ekstrand (2017-07-07 21:37:29)
The reason we were doing this was to ensure that the kernel did the
appropriate cross-ring synchronization and flushing. However, the
kernel only looks at EXEC_OBJECT_WRITE to determine whether or not
Quoting Jason Ekstrand (2017-07-07 21:37:29)
> The reason we were doing this was to ensure that the kernel did the
> appropriate cross-ring synchronization and flushing. However, the
> kernel only looks at EXEC_OBJECT_WRITE to determine whether or not to
> insert a fence. It only cares about the
The reason we were doing this was to ensure that the kernel did the
appropriate cross-ring synchronization and flushing. However, the
kernel only looks at EXEC_OBJECT_WRITE to determine whether or not to
insert a fence. It only cares about the domain for determining whether
or not it needs to clf
