AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: "Jani Nikula" <jani.nikula@linux.intel.com>,
	"Christian König" <christian.koenig@amd.com>,
	"Pierre-Eric Pelloux-Prayer" <pierre-eric.pelloux-prayer@amd.com>,
	dri-devel@lists.freedesktop.org, tursulin@igalia.com,
	simona.vetter@ffwll.ch, robdclark@gmail.com,
	alexander.deucher@amd.com, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH v4 0/6] DRM_SET_CLIENT_NAME ioctl
Date: Sat, 28 Sep 2024 15:34:11 +0300	[thread overview]
Message-ID: <e44c75a8-9747-424e-a1e5-e43d7ad43c2f@collabora.com> (raw)
In-Reply-To: <87ikuhzcad.fsf@intel.com>

On 9/27/24 12:16, Jani Nikula wrote:
> On Fri, 27 Sep 2024, Christian König <christian.koenig@amd.com> wrote:
>> Am 27.09.24 um 10:48 schrieb Pierre-Eric Pelloux-Prayer:
>>> v4 changelog:
>>> * DRM_SET_NAME -> DRM_SET_CLIENT_NAME (Dmitry)
>>> * reject names that would mess up with formatting (Sima),
>>>    and use a stricter filter (isgraph allowed extended ASCII
>>>    which weren't looking great)
>>> * documentation edits, minor fixups (Dmitry, Trvtko)
>>> * clarified commit message of commit 3/6 (Trvtko)
>>> * reworked amdgpu_vm_set_task_info a bit in 4/6 (Trvtko)
>>
>> If nobody has any more additional comments on this I'm going to pick it 
>> up and merge it through drm-misc-next by the end of today.
> 
> AFAICT the userspace is not reviewed and ready for merging [1].
> 
> BR,
> Jani.
> 
> 
> [1] https://gitlab.freedesktop.org/virgl/virglrenderer/-/merge_requests/1428

Userspace has been discussed in the past. I'll merge virglrenderer MR
once Pierre will update it based on this v4 and after the kernel patch
will land to misc-next.

-- 
Best regards,
Dmitry


      reply	other threads:[~2024-09-30  7:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-27  8:48 [PATCH v4 0/6] DRM_SET_CLIENT_NAME ioctl Pierre-Eric Pelloux-Prayer
2024-09-27  8:48 ` [PATCH v4 1/6] drm: add " Pierre-Eric Pelloux-Prayer
2024-09-28 12:31   ` Dmitry Osipenko
2024-09-30  8:57   ` Tvrtko Ursulin
2024-09-27  8:48 ` [PATCH v4 2/6] drm: use drm_file client_name in fdinfo Pierre-Eric Pelloux-Prayer
2024-09-27  8:48 ` [PATCH v4 3/6] drm/amdgpu: delay the use of amdgpu_vm_set_task_info Pierre-Eric Pelloux-Prayer
2024-09-27  8:48 ` [PATCH v4 4/6] drm/amdgpu: alloc and init vm::task_info from first submit Pierre-Eric Pelloux-Prayer
2024-09-27  8:48 ` [PATCH v4 5/6] drm/amdgpu: make process_name a flexible array Pierre-Eric Pelloux-Prayer
2024-09-27  8:48 ` [PATCH v4 6/6] drm/amdgpu: use drm_file::name in task_info::process_desc Pierre-Eric Pelloux-Prayer
2024-09-30  9:24   ` Tvrtko Ursulin
2024-09-27  9:07 ` [PATCH v4 0/6] DRM_SET_CLIENT_NAME ioctl Christian König
2024-09-27  9:16   ` Jani Nikula
2024-09-28 12:34     ` Dmitry Osipenko [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e44c75a8-9747-424e-a1e5-e43d7ad43c2f@collabora.com \
    --to=dmitry.osipenko@collabora.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=pierre-eric.pelloux-prayer@amd.com \
    --cc=robdclark@gmail.com \
    --cc=simona.vetter@ffwll.ch \
    --cc=tursulin@igalia.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox