From: Jay Cornwall <jay.cornwall@amd.com>
To: amd-gfx@lists.freedesktop.org
Cc: Lancelot Six <lancelot.six@amd.com>
Subject: Re: [PATCH v2] drm/amdkfd: Fix instruction hazard in gfx12 trap handler
Date: Thu, 27 Feb 2025 10:50:25 -0600 [thread overview]
Message-ID: <b40bb378-4651-45b2-b475-27b4076f94e2@amd.com> (raw)
In-Reply-To: <20250207233837.2738432-1-jay.cornwall@amd.com>
On 2/7/2025 17:38, Jay Cornwall wrote:
> VALU instructions with SGPR source need wait states to avoid hazard
> with SALU using different SGPR.
>
> v2: Eliminate some hazards to reduce code explosion
>
> Signed-off-by: Jay Cornwall <jay.cornwall@amd.com>
> Cc: Lancelot Six <lancelot.six@amd.com>
Ping.
next prev parent reply other threads:[~2025-02-27 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 23:38 [PATCH v2] drm/amdkfd: Fix instruction hazard in gfx12 trap handler Jay Cornwall
2025-02-27 16:50 ` Jay Cornwall [this message]
2025-02-27 16:53 ` Alex Deucher
2025-03-11 21:56 ` Lancelot SIX
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=b40bb378-4651-45b2-b475-27b4076f94e2@amd.com \
--to=jay.cornwall@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=lancelot.six@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