Displaying 3 results from an estimated 3 matches for "prove_lock".
Did you mean:
probe_lock
2014 Jul 22
2
[PATCH 09/17] drm/radeon: use common fence implementation for fences
...ry, like vmwgfx.
Ironically that is also a part of the ttm fence, except it was called flush there.
I would also like to note that ttm_bo_wait currently is also a function that currently uses is_signaled from atomic_context...
For the more complicated locking worries: Lockdep is your friend, use PROVE_LOCKING and find bugs before they trigger. ;-)
>> Like I've said I think restricting the insanity other people are willing
>> to live with just because you don't like it isn't right. But it is
>> certainly right for you to insist on not being forced into any such
>>...
2014 Jul 22
0
[PATCH 09/17] drm/radeon: use common fence implementation for fences
...side a single driver, no inter
driver needs here. We currently even call the internal fence
implementation from interrupt context as well and at more than one
occasion assume that TTM only uses radeon fences.
Christian.
> For the more complicated locking worries: Lockdep is your friend, use PROVE_LOCKING and find bugs before they trigger. ;-)
>
>>> Like I've said I think restricting the insanity other people are willing
>>> to live with just because you don't like it isn't right. But it is
>>> certainly right for you to insist on not being forced into an...
2014 Jul 22
3
[PATCH 09/17] drm/radeon: use common fence implementation for fences
On Tue, Jul 22, 2014 at 02:19:57PM +0200, Christian K?nig wrote:
> Am 22.07.2014 13:57, schrieb Daniel Vetter:
> >On Tue, Jul 22, 2014 at 01:46:07PM +0200, Daniel Vetter wrote:
> >>On Tue, Jul 22, 2014 at 10:43:13AM +0200, Christian K?nig wrote:
> >>>Am 22.07.2014 06:05, schrieb Dave Airlie:
> >>>>On 9 July 2014 22:29, Maarten Lankhorst