Re: [PATCH drm-next 13/14] drm/nouveau: implement new VM_BIND UAPI

2023-01-23 Thread Boris Brezillon
On Sun, 22 Jan 2023 17:48:37 + Matthew Brost wrote: > On Fri, Jan 20, 2023 at 11:22:45AM +0100, Boris Brezillon wrote: > > On Thu, 19 Jan 2023 16:38:06 + > > Matthew Brost wrote: > > > > > On Thu, Jan 19, 2023 at 04:36:43PM +0100, Danilo Krummrich wrote: > > > > On 1/19/23 05:58,

Re: [PATCH drm-next 13/14] drm/nouveau: implement new VM_BIND UAPI

2023-01-22 Thread Matthew Brost
On Fri, Jan 20, 2023 at 11:22:45AM +0100, Boris Brezillon wrote: > On Thu, 19 Jan 2023 16:38:06 + > Matthew Brost wrote: > > > On Thu, Jan 19, 2023 at 04:36:43PM +0100, Danilo Krummrich wrote: > > > On 1/19/23 05:58, Matthew Brost wrote: > > > > On Thu, Jan 19, 2023 at 04:44:23AM +0100,

Re: [PATCH drm-next 13/14] drm/nouveau: implement new VM_BIND UAPI

2023-01-20 Thread Boris Brezillon
On Thu, 19 Jan 2023 16:38:06 + Matthew Brost wrote: > On Thu, Jan 19, 2023 at 04:36:43PM +0100, Danilo Krummrich wrote: > > On 1/19/23 05:58, Matthew Brost wrote: > > > On Thu, Jan 19, 2023 at 04:44:23AM +0100, Danilo Krummrich wrote: > > > > On 1/18/23 21:37, Thomas Hellström (Intel)

Re: [PATCH drm-next 13/14] drm/nouveau: implement new VM_BIND UAPI

2023-01-20 Thread Boris Brezillon
On Thu, 19 Jan 2023 04:58:48 + Matthew Brost wrote: > > For the ops structures the drm_gpuva_manager allocates for reporting the > > split/merge steps back to the driver I have ideas to entirely avoid > > allocations, which also is a good thing in respect of Christians feedback > > regarding

Re: [PATCH drm-next 13/14] drm/nouveau: implement new VM_BIND UAPI

2023-01-19 Thread Matthew Brost
On Thu, Jan 19, 2023 at 11:25:51PM +0100, Danilo Krummrich wrote: > On 1/19/23 22:47, Matthew Brost wrote: > > On Thu, Jan 19, 2023 at 06:46:30PM +0100, Danilo Krummrich wrote: > > > > > > > > > On 1/19/23 17:38, Matthew Brost wrote: > > > > On Thu, Jan 19, 2023 at 04:36:43PM +0100, Danilo

Re: [PATCH drm-next 13/14] drm/nouveau: implement new VM_BIND UAPI

2023-01-19 Thread Danilo Krummrich
On 1/19/23 22:47, Matthew Brost wrote: On Thu, Jan 19, 2023 at 06:46:30PM +0100, Danilo Krummrich wrote: On 1/19/23 17:38, Matthew Brost wrote: On Thu, Jan 19, 2023 at 04:36:43PM +0100, Danilo Krummrich wrote: On 1/19/23 05:58, Matthew Brost wrote: On Thu, Jan 19, 2023 at 04:44:23AM +0100,

Re: [PATCH drm-next 13/14] drm/nouveau: implement new VM_BIND UAPI

2023-01-19 Thread Matthew Brost
On Thu, Jan 19, 2023 at 06:46:30PM +0100, Danilo Krummrich wrote: > > > On 1/19/23 17:38, Matthew Brost wrote: > > On Thu, Jan 19, 2023 at 04:36:43PM +0100, Danilo Krummrich wrote: > > > On 1/19/23 05:58, Matthew Brost wrote: > > > > On Thu, Jan 19, 2023 at 04:44:23AM +0100, Danilo Krummrich

Re: [PATCH drm-next 13/14] drm/nouveau: implement new VM_BIND UAPI

2023-01-19 Thread Danilo Krummrich
On 1/19/23 17:38, Matthew Brost wrote: On Thu, Jan 19, 2023 at 04:36:43PM +0100, Danilo Krummrich wrote: On 1/19/23 05:58, Matthew Brost wrote: On Thu, Jan 19, 2023 at 04:44:23AM +0100, Danilo Krummrich wrote: On 1/18/23 21:37, Thomas Hellström (Intel) wrote: On 1/18/23 07:12, Danilo

Re: [PATCH drm-next 13/14] drm/nouveau: implement new VM_BIND UAPI

2023-01-19 Thread Matthew Brost
On Thu, Jan 19, 2023 at 04:36:43PM +0100, Danilo Krummrich wrote: > On 1/19/23 05:58, Matthew Brost wrote: > > On Thu, Jan 19, 2023 at 04:44:23AM +0100, Danilo Krummrich wrote: > > > On 1/18/23 21:37, Thomas Hellström (Intel) wrote: > > > > > > > > On 1/18/23 07:12, Danilo Krummrich wrote: > > >

Re: [PATCH drm-next 13/14] drm/nouveau: implement new VM_BIND UAPI

2023-01-19 Thread Danilo Krummrich
On 1/19/23 05:58, Matthew Brost wrote: On Thu, Jan 19, 2023 at 04:44:23AM +0100, Danilo Krummrich wrote: On 1/18/23 21:37, Thomas Hellström (Intel) wrote: On 1/18/23 07:12, Danilo Krummrich wrote: This commit provides the implementation for the new uapi motivated by the Vulkan API. It allows

Re: [PATCH drm-next 13/14] drm/nouveau: implement new VM_BIND UAPI

2023-01-18 Thread Intel
On 1/19/23 05:58, Matthew Brost wrote: On Thu, Jan 19, 2023 at 04:44:23AM +0100, Danilo Krummrich wrote: On 1/18/23 21:37, Thomas Hellström (Intel) wrote: On 1/18/23 07:12, Danilo Krummrich wrote: This commit provides the implementation for the new uapi motivated by the Vulkan API. It

Re: [PATCH drm-next 13/14] drm/nouveau: implement new VM_BIND UAPI

2023-01-18 Thread Matthew Brost
On Thu, Jan 19, 2023 at 04:44:23AM +0100, Danilo Krummrich wrote: > On 1/18/23 21:37, Thomas Hellström (Intel) wrote: > > > > On 1/18/23 07:12, Danilo Krummrich wrote: > > > This commit provides the implementation for the new uapi motivated by the > > > Vulkan API. It allows user mode drivers

Re: [PATCH drm-next 13/14] drm/nouveau: implement new VM_BIND UAPI

2023-01-18 Thread Danilo Krummrich
On 1/18/23 21:37, Thomas Hellström (Intel) wrote: On 1/18/23 07:12, Danilo Krummrich wrote: This commit provides the implementation for the new uapi motivated by the Vulkan API. It allows user mode drivers (UMDs) to: 1) Initialize a GPU virtual address (VA) space via the new    

Re: [PATCH drm-next 13/14] drm/nouveau: implement new VM_BIND UAPI

2023-01-18 Thread Intel
On 1/18/23 07:12, Danilo Krummrich wrote: This commit provides the implementation for the new uapi motivated by the Vulkan API. It allows user mode drivers (UMDs) to: 1) Initialize a GPU virtual address (VA) space via the new DRM_IOCTL_NOUVEAU_VM_INIT ioctl for UMDs to specify the portion

[PATCH drm-next 13/14] drm/nouveau: implement new VM_BIND UAPI

2023-01-17 Thread Danilo Krummrich
This commit provides the implementation for the new uapi motivated by the Vulkan API. It allows user mode drivers (UMDs) to: 1) Initialize a GPU virtual address (VA) space via the new DRM_IOCTL_NOUVEAU_VM_INIT ioctl for UMDs to specify the portion of VA space managed by the kernel and