Hi guys,
a few more bug fixes, looks like the more selftests I add the more odies I find.
Assuming the CI tests now pass I will start pushing patches I've already got an
rb for to drm-misc-next.
Please review and/or comment,
Christian.
Hi guys,
I've fixed up the lockdep splat in the new selftests found by the CI
systems and added another path for dma_resv_poll.
I know you guys are flooded, but can we get at least the first few patches
committed? The patches to change the individual drivers could also be pushed
later on I think
Hi guys,
The version I've send out yesterday had a rather obvious coding error and I
honestly forgot the cover letter.
This one here is better tested and will now hopefully not be torn apart from
the CI system immediately.
I tried to address all review and documentation comments as best as I c
Hopefully the last round for this.
Added dma_resv_iter_begin/end as requested by Daniel. Fixed a bunch of
problems pointed out by the CI systems and found a few more myselve.
Please review and/or comment,
Christian.
Next round for that one here, maybe the CI systems are now more
gracefully with me :)
I'm pretty sure that a couple of those dma_resv_for_each_fence_unlocked
should actually be replaced with lock+dma_resv_for_each_fence, but that
needs more auditing.
Please review and comment.
Thanks,
Christian.
Hi everybody,
we recently found that a good bunch of the RCU accesses to the dma_resv object
are actually not correctly protected.
Those where fixed by either dropping the RCU approach and taking appropriate
locks or using a central function to return the current fences as array and
then work
