On 19 April 2017 at 07:55, Jason Ekstrand wrote:
> A few thoughts (from the anv perspective) that I put on IRC but may be
> better in a mail. In no particular order:
>
> 1. Having the fd exported from a syncobj be a valid sync_file seems like a
> fairly pointless feature to me. If we can make t
A few thoughts (from the anv perspective) that I put on IRC but may be
better in a mail. In no particular order:
1. Having the fd exported from a syncobj be a valid sync_file seems like a
fairly pointless feature to me. If we can make things more sane by
throwing that out, I'm all for it.
2.
On Wed, Apr 19, 2017 at 05:34:52AM +1000, Dave Airlie wrote:
> On 14 April 2017 at 19:45, Chris Wilson wrote:
> > On Tue, Apr 11, 2017 at 01:22:12PM +1000, Dave Airlie wrote:
> >> This set of sync object patches should address most of the issues
> >> raised in review.
> >>
> >> The major changes:
On 14 April 2017 at 19:45, Chris Wilson wrote:
> On Tue, Apr 11, 2017 at 01:22:12PM +1000, Dave Airlie wrote:
>> This set of sync object patches should address most of the issues
>> raised in review.
>>
>> The major changes:
>> Race on destroy should be gone,
>> Documentation fixups
>> amdgpu inte
On Tue, Apr 11, 2017 at 01:22:12PM +1000, Dave Airlie wrote:
> This set of sync object patches should address most of the issues
> raised in review.
>
> The major changes:
> Race on destroy should be gone,
> Documentation fixups
> amdgpu internal use p instead of adev fixups
>
> My plans are to w
This set of sync object patches should address most of the issues
raised in review.
The major changes:
Race on destroy should be gone,
Documentation fixups
amdgpu internal use p instead of adev fixups
My plans are to write some igt tests this week, and try
to get some more review on what the API
