mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: Lizhi Hou <lizhi.hou@amd.com>,
	ogabbay@kernel.org, quic_jhugo@quicinc.com,
	dri-devel@lists.freedesktop.org,
	maciej.falkowski@linux.intel.com
Cc: Max Zhen <max.zhen@amd.com>,
	linux-kernel@vger.kernel.org, sonal.santan@amd.com
Subject: Re: [PATCH V1] accel/amdxdna: Fix fatal_error_info layout in firmware interface
Date: Tue, 14 Apr 2026 11:59:08 -0500	[thread overview]
Message-ID: <19e31c05-4ae4-448f-a9fa-7961230a2349@amd.com> (raw)
In-Reply-To: <20260414165625.788853-1-lizhi.hou@amd.com>



On 4/14/26 11:56, Lizhi Hou wrote:
> From: Max Zhen <max.zhen@amd.com>
> 
> Adjust struct fatal_error_info to match the expected driver/firmware
> interface layout.
> 
> The structure is used to retrieve debug information from firmware when
> a command becomes stuck on the device. The reserved field currently
> uses 128 u32 entries, which makes the structure larger than intended
> and causes the layout to no longer match the firmware definition.
> 
> Reduce the reserved array size from 128 to 127 entries so the
> structure matches the expected interface format.
> 
> Fixes: 25854131c04a ("accel/amdxdna: Support retrieving hardware context debug information")
> Signed-off-by: Max Zhen <max.zhen@amd.com>
> Signed-off-by: Lizhi Hou <lizhi.hou@amd.com>
Reviewed-by: Mario Limonciello (AMD) <superm1@kernel.org>

> ---
>   drivers/accel/amdxdna/aie2_msg_priv.h | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/accel/amdxdna/aie2_msg_priv.h b/drivers/accel/amdxdna/aie2_msg_priv.h
> index fc2e99510980..b10552c627ee 100644
> --- a/drivers/accel/amdxdna/aie2_msg_priv.h
> +++ b/drivers/accel/amdxdna/aie2_msg_priv.h
> @@ -461,7 +461,7 @@ struct fatal_error_info {
>   	__u32 exception_pc;       /* Program Counter at the time of the exception */
>   	__u32 app_module;         /* Error module name */
>   	__u32 task_index;         /* Index of the task in which the error occurred */
> -	__u32 reserved[128];
> +	__u32 reserved[127];
>   };
>   
>   struct app_health_report {


  reply	other threads:[~2026-04-14 16:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-14 16:56 Lizhi Hou
2026-04-14 16:59 ` Mario Limonciello [this message]
2026-04-15 18:06   ` Lizhi Hou

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=19e31c05-4ae4-448f-a9fa-7961230a2349@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizhi.hou@amd.com \
    --cc=maciej.falkowski@linux.intel.com \
    --cc=max.zhen@amd.com \
    --cc=ogabbay@kernel.org \
    --cc=quic_jhugo@quicinc.com \
    --cc=sonal.santan@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

all inboxes | Powered by JetHome®