Displaying 2 results from an estimated 2 matches for "022388".
Did you mean:
22388
2014 May 19
2
[RFC PATCH v1 08/16] drm/radeon: use common fence implementation for fences
Am 19.05.2014 12:10, schrieb Maarten Lankhorst:
> op 19-05-14 10:27, Christian K?nig schreef:
>> Am 19.05.2014 10:00, schrieb Maarten Lankhorst:
>> [SNIP]
>> The problem here is that the whole approach collides with the way we
>> do reset handling from a conceptual point of view. Every IOCTL or
>> other call chain into the driver is protected by the read side of
2014 May 19
2
[RFC PATCH v1 08/16] drm/radeon: use common fence implementation for fences
...the interface.
>
And this is what I'm suggesting here.
We have avoided quite hard adding any form of those callbacks in the
past and I don't really see a reason why that would have changed. For
example see the discussion here:
http://lists.freedesktop.org/archives/dri-devel/2012-May/022388.html
Jerome and Dave rejected my approach for handling the sub allocator
through a callback for exactly the same reason. And that was even for
call chains inside the same driver, you're suggesting this for cross
driver synchronization.
Christian.