From: "Christian König" <christian.koenig@amd.com>
To: Sunil Khatri <sunil.khatri@amd.com>,
Alex Deucher <alexander.deucher@amd.com>
Cc: amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/amdgpu/userq: update the vm task info during signal ioctl
Date: Tue, 12 May 2026 12:39:23 +0200 [thread overview]
Message-ID: <5d6f5153-628a-47fa-be0c-eae8f2851113@amd.com> (raw)
In-Reply-To: <20260512103208.1012595-1-sunil.khatri@amd.com>
On 5/12/26 12:32, Sunil Khatri wrote:
> Pagefaults does not have process information correctly populated
> as vm->task is not set during vm_init but should be updated while
> real submission. So setting that up during signal_ioctl to get
> the correct submission process details.
>
> Signed-off-by: Sunil Khatri <sunil.khatri@amd.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_userq_fence.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_userq_fence.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_userq_fence.c
> index 008330a0d852..1dcde9b35f8b 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_userq_fence.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_userq_fence.c
> @@ -514,6 +514,9 @@ int amdgpu_userq_signal_ioctl(struct drm_device *dev, void *data,
> goto put_gobj_write;
> }
>
> + /* Update VM owner at userq submit-time for page-fault attribution. */
> + amdgpu_vm_set_task_info(&fpriv->vm);
> +
Doing that in the signal IOCTL is probably a bit overkill since it is used quite often during the lifetime of the queue.
We can't add it to the userq manager creation because that is often done by X/Wayland instead of the final application, but I think we can just add it to the queue creation.
That should always be done in the process which is going to use the queue.
Regards,
Christian.
> r = amdgpu_userq_fence_read_wptr(adev, queue, &wptr);
> if (r)
> goto put_queue;
next prev parent reply other threads:[~2026-05-12 10:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 10:32 [PATCH] drm/amdgpu/userq: update the vm task info during signal ioctl Sunil Khatri
2026-05-12 10:39 ` Christian König [this message]
2026-05-12 10:49 ` Khatri, Sunil
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=5d6f5153-628a-47fa-be0c-eae8f2851113@amd.com \
--to=christian.koenig@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=sunil.khatri@amd.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