Re: [PATCH 3/4] drm/doc/rfc: Mark DRM_VM_BIND as complete.

2023-09-06 Thread Rodrigo Vivi
On Mon, Sep 04, 2023 at 11:32:30PM +0200, Danilo Krummrich wrote: > Hi Rodrigo, > > On 8/31/23 21:10, Rodrigo Vivi wrote: > > On Tue, Aug 29, 2023 at 12:30:03PM -0400, Rodrigo Vivi wrote: > > > The consensus is for individual drivers VM_BIND uapis with > > > the GPUVA helpers that are already

Re: [PATCH 3/4] drm/doc/rfc: Mark DRM_VM_BIND as complete.

2023-09-04 Thread Danilo Krummrich
Hi Rodrigo, On 8/31/23 21:10, Rodrigo Vivi wrote: On Tue, Aug 29, 2023 at 12:30:03PM -0400, Rodrigo Vivi wrote: The consensus is for individual drivers VM_BIND uapis with the GPUVA helpers that are already implemented and merged upstream. The merged GPUVA documentation also establish some

Re: [PATCH 3/4] drm/doc/rfc: Mark DRM_VM_BIND as complete.

2023-08-31 Thread Rodrigo Vivi
On Tue, Aug 29, 2023 at 12:30:03PM -0400, Rodrigo Vivi wrote: > The consensus is for individual drivers VM_BIND uapis with > the GPUVA helpers that are already implemented and merged > upstream. > > The merged GPUVA documentation also establish some overall > rules for the locking to be followed

[PATCH 3/4] drm/doc/rfc: Mark DRM_VM_BIND as complete.

2023-08-29 Thread Rodrigo Vivi
The consensus is for individual drivers VM_BIND uapis with the GPUVA helpers that are already implemented and merged upstream. The merged GPUVA documentation also establish some overall rules for the locking to be followed by the drivers. Signed-off-by: Rodrigo Vivi ---