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

2023-11-13 Thread Gurchetan Singh
On Sat, Nov 11, 2023 at 2:37 PM Dmitry Osipenko < dmitry.osipe...@collabora.com> wrote: > On 10/18/23 21:17, Gurchetan Singh wrote: > > + case VIRTGPU_CONTEXT_PARAM_DEBUG_NAME: > > + if (vfpriv->explicit_debug_name) { > > + ret = -EINVAL;

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

2023-11-11 Thread Dmitry Osipenko
On 10/18/23 21:17, Gurchetan Singh wrote: > + case VIRTGPU_CONTEXT_PARAM_DEBUG_NAME: > + if (vfpriv->explicit_debug_name) { > + ret = -EINVAL; > + goto out_unlock; > + } > + > +

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

2023-11-11 Thread Dmitry Osipenko
On 10/18/23 21:17, 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 around

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

2023-11-10 Thread Gurchetan Singh
On Tue, Oct 31, 2023 at 8:55 AM Gurchetan Singh wrote: > > > On Sun, Oct 22, 2023 at 4:50 PM Dmitry Osipenko < > dmitry.osipe...@collabora.com> wrote: > >> On 10/18/23 21:17, Gurchetan Singh wrote: >> > There are two problems with the current method of determining the >> > virtio-gpu debug name.

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

2023-10-31 Thread Gurchetan Singh
On Sun, Oct 22, 2023 at 4:50 PM Dmitry Osipenko < dmitry.osipe...@collabora.com> wrote: > On 10/18/23 21:17, 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

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

2023-10-22 Thread Dmitry Osipenko
On 10/18/23 21:17, 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 around

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

2023-10-18 Thread Dmitry Osipenko
On 10/18/23 21:17, 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 around

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

2023-10-18 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.