Re: RFC: dma_resv_unlock() and ww_acquire_ctx scope

2023-01-24 Thread Paul Cercueil
Le jeudi 19 janvier 2023 à 12:44 +0100, Christian König a écrit : > Am 19.01.23 um 12:12 schrieb Daniel Vetter: > > On Thu, Jan 19, 2023 at 11:37:39AM +0100, Maarten Lankhorst wrote: > > > On 2023-01-19 11:24, Paul Cercueil wrote: > > > > Hi, > > > > > > > > Just a reflexion I have after an intens

Re: RFC: dma_resv_unlock() and ww_acquire_ctx scope

2023-01-19 Thread Christian König
Am 19.01.23 um 12:12 schrieb Daniel Vetter: On Thu, Jan 19, 2023 at 11:37:39AM +0100, Maarten Lankhorst wrote: On 2023-01-19 11:24, Paul Cercueil wrote: Hi, Just a reflexion I have after an intensive (and intense) debugging session. I had the following code: int my_dma_resv_lock(struct dma_

Re: RFC: dma_resv_unlock() and ww_acquire_ctx scope

2023-01-19 Thread Daniel Vetter
On Thu, Jan 19, 2023 at 11:37:39AM +0100, Maarten Lankhorst wrote: > > On 2023-01-19 11:24, Paul Cercueil wrote: > > Hi, > > > > Just a reflexion I have after an intensive (and intense) debugging > > session. > > > > I had the following code: > > > > > > int my_dma_resv_lock(struct dma_buf *dm

Re: RFC: dma_resv_unlock() and ww_acquire_ctx scope

2023-01-19 Thread Maarten Lankhorst
On 2023-01-19 11:24, Paul Cercueil wrote: Hi, Just a reflexion I have after an intensive (and intense) debugging session. I had the following code: int my_dma_resv_lock(struct dma_buf *dmabuf) { struct ww_acquire_ctx ctx; int ret; ww_acquire_init(&ctx, &reservation_