AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lancelot SIX <Lancelot.Six@amd.com>
To: Jonathan Kim <jonathan.kim@amd.com>, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/amdkfd: set precise mem ops caps to disabled for gfx 11 and 12
Date: Mon, 17 Mar 2025 11:01:57 +0000	[thread overview]
Message-ID: <409bc442-cf25-4a5a-862e-6eb8376c0584@amd.com> (raw)
In-Reply-To: <20250314151416.726789-1-jonathan.kim@amd.com>



On 14/03/2025 15:14, Jonathan Kim wrote:
> Clause instructions with precise memory enabled currently hang the
> shader so set capabilities flag to disabled since it's unsafe to use
> for debugging.
> 
> Signed-off-by: Jonathan Kim <jonathan.kim@amd.com>

Hi,

I have tested this for gfx11.
For what it is worth, this patch looks to me.

Tested-by: Lancelot Six <lancelot.six@amd.com>

Best,
Lancelot.

> ---
>   drivers/gpu/drm/amd/amdkfd/kfd_topology.c | 4 ----
>   1 file changed, 4 deletions(-)
> 
> diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_topology.c b/drivers/gpu/drm/amd/amdkfd/kfd_topology.c
> index 27e7356eed6f..e477d7509646 100644
> --- a/drivers/gpu/drm/amd/amdkfd/kfd_topology.c
> +++ b/drivers/gpu/drm/amd/amdkfd/kfd_topology.c
> @@ -2006,10 +2006,6 @@ static void kfd_topology_set_capabilities(struct kfd_topology_device *dev)
>   		dev->node_props.debug_prop |= HSA_DBG_WATCH_ADDR_MASK_LO_BIT_GFX10 |
>   					HSA_DBG_WATCH_ADDR_MASK_HI_BIT;
>   
> -		if (KFD_GC_VERSION(dev->gpu) >= IP_VERSION(11, 0, 0))
> -			dev->node_props.capability |=
> -				HSA_CAP_TRAP_DEBUG_PRECISE_MEMORY_OPERATIONS_SUPPORTED;
> -
>   		if (KFD_GC_VERSION(dev->gpu) >= IP_VERSION(12, 0, 0))
>   			dev->node_props.capability |=
>   				HSA_CAP_TRAP_DEBUG_PRECISE_ALU_OPERATIONS_SUPPORTED;


  reply	other threads:[~2025-03-17 11:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-14 15:14 [PATCH] drm/amdkfd: set precise mem ops caps to disabled for gfx 11 and 12 Jonathan Kim
2025-03-17 11:01 ` Lancelot SIX [this message]
2025-03-17 20:40   ` Kasiviswanathan, Harish

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=409bc442-cf25-4a5a-862e-6eb8376c0584@amd.com \
    --to=lancelot.six@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=jonathan.kim@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