From: "Christian König" <christian.koenig@amd.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>,
Alex Deucher <alexander.deucher@amd.com>
Cc: lijo.lazar@amd.com, Eric Huang <jinhuieric.huang@amd.com>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/amdgpu: use IRQ-safe xarray API for PASID management
Date: Wed, 1 Apr 2026 12:25:59 +0200 [thread overview]
Message-ID: <f7ba4ef3-e397-449a-af92-0c27b4b6dd4e@amd.com> (raw)
In-Reply-To: <20260401073632.101796-1-mikhail.v.gavrilov@gmail.com>
On 4/1/26 09:36, Mikhail Gavrilov wrote:
> xa_alloc_cyclic() and xa_erase() use plain xa_lock()/xa_unlock()
> regardless of XA_FLAGS_LOCK_IRQ — the flag only affects lockdep
> annotations, not runtime locking.
>
> Switch to xa_alloc_cyclic_irq() and xa_erase_irq() which use
> xa_lock_irq/xa_unlock_irq internally, fixing the IRQ safety issue
> for amdgpu_pasid_free() called from hardirq via fence callbacks.
>
> Fixes: a3c0ee978e16 ("drm/amdgpu: replace PASID IDR with XArray")
> Signed-off-by: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_ids.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_ids.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_ids.c
> index a6ac3b4ce0df..64d0da28441f 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_ids.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_ids.c
> @@ -68,7 +68,7 @@ int amdgpu_pasid_alloc(unsigned int bits)
> if (bits == 0)
> return -EINVAL;
>
> - r = xa_alloc_cyclic(&amdgpu_pasid_xa, &pasid, xa_mk_value(0),
> + r = xa_alloc_cyclic_irq(&amdgpu_pasid_xa, &pasid, xa_mk_value(0),
> XA_LIMIT(1, (1U << bits) - 1),
> &amdgpu_pasid_xa_next, GFP_KERNEL);
> if (r < 0)
> @@ -85,7 +85,7 @@ int amdgpu_pasid_alloc(unsigned int bits)
> void amdgpu_pasid_free(u32 pasid)
> {
> trace_amdgpu_pasid_freed(pasid);
> - xa_erase(&amdgpu_pasid_xa, pasid);
> + xa_erase_irq(&amdgpu_pasid_xa, pasid);
This one needs to use:
xa_lock_irqsave(xa, flags);
__xa_eras(...);
xa_unlock_irqrestore(xa, flags);
Since it is actually used in IRQ context and not process context.
Apart from that looks good to me.
Regards,
Christian.
> }
>
> static void amdgpu_pasid_free_cb(struct dma_fence *fence,
prev parent reply other threads:[~2026-04-01 10:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 7:36 [PATCH] drm/amdgpu: use IRQ-safe xarray API for PASID management Mikhail Gavrilov
2026-04-01 10:25 ` Christian König [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=f7ba4ef3-e397-449a-af92-0c27b4b6dd4e@amd.com \
--to=christian.koenig@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jinhuieric.huang@amd.com \
--cc=lijo.lazar@amd.com \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=simona@ffwll.ch \
/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