From: Felix Kuehling <felix.kuehling@amd.com>
To: Jonathan Kim <jonathan.kim@amd.com>, amd-gfx@lists.freedesktop.org
Cc: JinHuiEric.Huang@amd.com
Subject: Re: [PATCH] drm/amdkfd: report dispatch id always saved in ttmps after gc9.4.2
Date: Tue, 11 Jul 2023 14:32:54 -0400 [thread overview]
Message-ID: <eba2d296-e694-ecc6-9568-39f505b2517f@amd.com> (raw)
In-Reply-To: <20230711171947.2914493-1-jonathan.kim@amd.com>
On 2023-07-11 13:19, Jonathan Kim wrote:
> The feature to save the dispatch ID in trap temporaries 6 & 7 on context
> save is unconditionally enabled during MQD initialization.
>
> Now that TTMPs are always setup regardless of debug mode for GC 9.4.3, we
> should report that the dispatch ID is always available for debug/trap
> handling.
>
> Signed-off-by: Jonathan Kim <jonathan.kim@amd.com>
Reviewed-by: Felix Kuehling <Felix.Kuehling@amd.com>
> ---
> drivers/gpu/drm/amd/amdkfd/kfd_topology.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_topology.c b/drivers/gpu/drm/amd/amdkfd/kfd_topology.c
> index 1a4cdee86759..eeedc3ddffeb 100644
> --- a/drivers/gpu/drm/amd/amdkfd/kfd_topology.c
> +++ b/drivers/gpu/drm/amd/amdkfd/kfd_topology.c
> @@ -1941,10 +1941,11 @@ static void kfd_topology_set_capabilities(struct kfd_topology_device *dev)
> HSA_DBG_WATCH_ADDR_MASK_LO_BIT_GFX9 |
> HSA_DBG_WATCH_ADDR_MASK_HI_BIT;
>
> - if (KFD_GC_VERSION(dev->gpu) < IP_VERSION(9, 4, 2))
> + if (KFD_GC_VERSION(dev->gpu) != IP_VERSION(9, 4, 2))
> dev->node_props.debug_prop |=
> HSA_DBG_DISPATCH_INFO_ALWAYS_VALID;
> - else
> +
> + if (KFD_GC_VERSION(dev->gpu) >= IP_VERSION(9, 4, 2))
> dev->node_props.capability |=
> HSA_CAP_TRAP_DEBUG_PRECISE_MEMORY_OPERATIONS_SUPPORTED;
> } else {
prev parent reply other threads:[~2023-07-11 18:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 17:19 [PATCH] drm/amdkfd: report dispatch id always saved in ttmps after gc9.4.2 Jonathan Kim
2023-07-11 18:32 ` Felix Kuehling [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=eba2d296-e694-ecc6-9568-39f505b2517f@amd.com \
--to=felix.kuehling@amd.com \
--cc=JinHuiEric.Huang@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