Re: completely rework the dma_resv semantic

2022-02-18 Thread Christian König
Daniel any estimation when you will have time to take a closer look? Or could anybody else take another look at this? Thanks, Christian. Am 11.02.22 um 13:49 schrieb Christian König: Hi guys, by now that should be a rather well known set of changes. The basic idea is that instead of the fixe

completely rework the dma_resv semantic

2022-02-11 Thread Christian König
Hi guys, by now that should be a rather well known set of changes. The basic idea is that instead of the fixed exclusive/shared classes we now attach an usage to each fence in the dma_resv object describing how the operation represented by the fence is using the resources protected by the dma_res

Re: completely rework the dma_resv semantic

2022-01-14 Thread Daniel Vetter
On Thu, Dec 23, 2021 at 10:11:20AM +0100, Christian König wrote: > Am 22.12.21 um 23:17 schrieb Daniel Vetter: > > On Fri, Dec 17, 2021 at 03:39:52PM +0100, Christian König wrote: > > > Hi Daniel, > > > > > > looks like this is going nowhere and you don't seem to have time to > > > review. > > >

Re: completely rework the dma_resv semantic

2021-12-23 Thread Christian König
Am 22.12.21 um 23:17 schrieb Daniel Vetter: On Fri, Dec 17, 2021 at 03:39:52PM +0100, Christian König wrote: Hi Daniel, looks like this is going nowhere and you don't seem to have time to review. What can we do? cc more people, you didn't cc any of the driver folks :-) Well I've CCed more p

Re: completely rework the dma_resv semantic

2021-12-22 Thread Daniel Vetter
On Fri, Dec 17, 2021 at 03:39:52PM +0100, Christian König wrote: > Hi Daniel, > > looks like this is going nowhere and you don't seem to have time to review. > > What can we do? cc more people, you didn't cc any of the driver folks :-) Also I did find some review before I disappeared, back on 1

Re: completely rework the dma_resv semantic

2021-12-17 Thread Christian König
Hi Daniel, looks like this is going nowhere and you don't seem to have time to review. What can we do? Thanks, Christian. Am 07.12.21 um 13:33 schrieb Christian König: Hi Daniel, just a gentle ping that you wanted to take a look at this. Not much changed compared to the last version, only a

completely rework the dma_resv semantic

2021-12-07 Thread Christian König
Hi Daniel, just a gentle ping that you wanted to take a look at this. Not much changed compared to the last version, only a minor bugfix in the dma_resv_get_singleton error handling. Regards, Christian.

completely rework the dma_resv semantic

2021-11-29 Thread Christian König
Hi everyone, compared to the last version I've dropped the pruning as suggested by Maarten, split the new DMA_RESV_USAGE_* patches from the general introduction as suggeted by Daniel and renamed OTEHRS to BOOKKEEP as suggested by Pekka. Please take a look and review, Christian.

Re: completely rework the dma_resv semantic

2021-11-25 Thread Daniel Vetter
On Tue, Nov 23, 2021 at 03:20:45PM +0100, Christian König wrote: > Hi guys, > > as discussed before this set of patches completely rework the dma_resv > semantic > and spreads the new handling over all the existing drivers and users. > > First of all this drops the DA

Re: completely rework the dma_resv semantic

2021-11-24 Thread Christian König
Am 24.11.21 um 09:31 schrieb Pekka Paalanen: On Tue, 23 Nov 2021 15:20:45 +0100 "Christian König" wrote: Hi guys, as discussed before this set of patches completely rework the dma_resv semantic and spreads the new handling over all the existing drivers and users. First of all this

Re: completely rework the dma_resv semantic

2021-11-24 Thread Pekka Paalanen
On Tue, 23 Nov 2021 15:20:45 +0100 "Christian König" wrote: > Hi guys, > > as discussed before this set of patches completely rework the dma_resv > semantic > and spreads the new handling over all the existing drivers and users. > > First of all this drops the D

completely rework the dma_resv semantic

2021-11-23 Thread Christian König
Hi guys, as discussed before this set of patches completely rework the dma_resv semantic and spreads the new handling over all the existing drivers and users. First of all this drops the DAG approach because it requires that every single driver implements those relatively complicated rules