AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Harish Kasiviswanathan <harish.kasiviswanathan@amd.com>
To: Jonathan Kim <jonathan.kim@amd.com>, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/amdkfd: flag per-queue reset support for gfx9
Date: Mon, 28 Oct 2024 10:38:37 -0400	[thread overview]
Message-ID: <922d37b6-c8c6-4e30-970c-d15f9d160fd1@amd.com> (raw)
In-Reply-To: <20241022173657.2363931-1-jonathan.kim@amd.com>

Reviewed-by: Harish Kasiviswanathan <Harish.Kasiviswanathan@amd.com>


On 2024-10-22 13:36, Jonathan Kim wrote:
> Flag KFD support for per-queue reset on GFX9 devices.
> 
> Signed-off-by: Jonathan Kim <jonathan.kim@amd.com>
> ---
>  drivers/gpu/drm/amd/amdkfd/kfd_topology.c | 2 ++
>  include/uapi/linux/kfd_sysfs.h            | 3 ++-
>  2 files changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_topology.c b/drivers/gpu/drm/amd/amdkfd/kfd_topology.c
> index 3871591c9aec..9476e30d6baa 100644
> --- a/drivers/gpu/drm/amd/amdkfd/kfd_topology.c
> +++ b/drivers/gpu/drm/amd/amdkfd/kfd_topology.c
> @@ -1998,6 +1998,8 @@ static void kfd_topology_set_capabilities(struct kfd_topology_device *dev)
>  		if (KFD_GC_VERSION(dev->gpu) >= IP_VERSION(9, 4, 2))
>  			dev->node_props.capability |=
>  				HSA_CAP_TRAP_DEBUG_PRECISE_MEMORY_OPERATIONS_SUPPORTED;
> +
> +		dev->node_props.capability |= HSA_CAP_PER_QUEUE_RESET_SUPPORTED;
>  	} else {
>  		dev->node_props.debug_prop |= HSA_DBG_WATCH_ADDR_MASK_LO_BIT_GFX10 |
>  					HSA_DBG_WATCH_ADDR_MASK_HI_BIT;
> diff --git a/include/uapi/linux/kfd_sysfs.h b/include/uapi/linux/kfd_sysfs.h
> index 5e8d28617efa..859b8e91d4d3 100644
> --- a/include/uapi/linux/kfd_sysfs.h
> +++ b/include/uapi/linux/kfd_sysfs.h
> @@ -60,7 +60,8 @@
>  #define HSA_CAP_FLAGS_COHERENTHOSTACCESS			0x10000000
>  #define HSA_CAP_TRAP_DEBUG_FIRMWARE_SUPPORTED			0x20000000
>  #define HSA_CAP_TRAP_DEBUG_PRECISE_ALU_OPERATIONS_SUPPORTED	0x40000000
> -#define HSA_CAP_RESERVED					0x800f8000
> +#define HSA_CAP_PER_QUEUE_RESET_SUPPORTED			0x80000000
> +#define HSA_CAP_RESERVED					0x000f8000
>  
>  /* debug_prop bits in node properties */
>  #define HSA_DBG_WATCH_ADDR_MASK_LO_BIT_MASK     0x0000000f

      reply	other threads:[~2024-10-28 14:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-22 17:36 [PATCH] drm/amdkfd: flag per-queue reset support for gfx9 Jonathan Kim
2024-10-28 14:38 ` Harish Kasiviswanathan [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=922d37b6-c8c6-4e30-970c-d15f9d160fd1@amd.com \
    --to=harish.kasiviswanathan@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