Re: [PATCH 2/3] drm/uapi: add explicit virtgpu context debug name

2023-10-16 Thread Dmitry Osipenko
On 10/16/23 21:41, Gurchetan Singh wrote: > There are two problems with the current method of determining the > virtio-gpu debug name. > > 1) TASK_COMM_LEN is defined to be 16 bytes only, and this is a >Linux kernel idiom (see PR_SET_NAME + PR_GET_NAME). Though, >Android/FreeBSD get

Re: [PATCH 2/3] drm/uapi: add explicit virtgpu context debug name

2023-10-16 Thread Josh Simonot
Reviewed-by: Josh Simonot On Mon, 16 Oct 2023 at 14:42, Gurchetan Singh wrote: > There are two problems with the current method of determining the > virtio-gpu debug name. > > 1) TASK_COMM_LEN is defined to be 16 bytes only, and this is a >Linux kernel idiom (see PR_SET_NAME +

[PATCH 2/3] drm/uapi: add explicit virtgpu context debug name

2023-10-16 Thread Gurchetan Singh
There are two problems with the current method of determining the virtio-gpu debug name. 1) TASK_COMM_LEN is defined to be 16 bytes only, and this is a Linux kernel idiom (see PR_SET_NAME + PR_GET_NAME). Though, Android/FreeBSD get around this via setprogname(..)/getprogname(..) in libc.