From: Lancelot SIX <Lancelot.Six@amd.com>
To: Jay Cornwall <jay.cornwall@amd.com>, amd-gfx@lists.freedesktop.org
Cc: Vladimir Indic <vladimir.indic@amd.com>
Subject: Re: [PATCH 4/5] drm/amdkfd: gfx12.1 trap handler support for expert scheduling mode
Date: Tue, 20 Jan 2026 23:30:12 +0000 [thread overview]
Message-ID: <1471efbb-6431-4a3f-8361-2666efa485c8@amd.com> (raw)
In-Reply-To: <20260116203932.988704-5-jay.cornwall@amd.com>
Hi,
Thanks, that looks good to me. Thanks.
Best,
Lancelot.
On 16/01/2026 20:39, Jay Cornwall wrote:
> - Leave DEP_MODE unchanged as it is ignored in the trap handler
> - Save/restore SCHED_MODE (gfx12.0 saves in ttmp11)
>
> Signed-off-by: Jay Cornwall <jay.cornwall@amd.com>
> Cc: Lancelot Six <lancelot.six@amd.com>
> Cc: Vladimir Indic <vladimir.indic@amd.com>
Reviewed-by: Lancelot Six <lancelot.six@amd.com>
next prev parent reply other threads:[~2026-01-20 23:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 20:39 [PATCH 0/5] drm/amdkfd: Trap handler fixes and gfx12.1 support Jay Cornwall
2026-01-16 20:39 ` [PATCH 1/5] drm/amdkfd: Sync trap handler binary with source Jay Cornwall
2026-01-20 22:34 ` Lancelot SIX
2026-01-21 10:27 ` Indic, Vladimir
2026-01-16 20:39 ` [PATCH 2/5] drm/amdkfd: Fix scalar load ordering in gfx12.1 trap handler Jay Cornwall
2026-01-20 22:38 ` Lancelot SIX
2026-01-21 10:32 ` Indic, Vladimir
2026-01-16 20:39 ` [PATCH 3/5] drm/amdkfd: gfx12.1 cluster barrier context save workaround Jay Cornwall
2026-01-20 23:27 ` Lancelot SIX
2026-01-21 10:37 ` Indic, Vladimir
2026-01-16 20:39 ` [PATCH 4/5] drm/amdkfd: gfx12.1 trap handler support for expert scheduling mode Jay Cornwall
2026-01-20 23:30 ` Lancelot SIX [this message]
2026-01-21 10:46 ` Indic, Vladimir
2026-01-16 20:39 ` [PATCH 5/5] drm/amdkfd: Do not include VGPR MSBs in saved PC during save Jay Cornwall
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=1471efbb-6431-4a3f-8361-2666efa485c8@amd.com \
--to=lancelot.six@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=jay.cornwall@amd.com \
--cc=vladimir.indic@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