From: John Harrison <john.c.harrison@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
<Intel-Xe@Lists.FreeDesktop.Org>
Subject: Re: [PATCH v3 2/4] drm/xe/guc: Add missing H2G error code definitions
Date: Mon, 12 May 2025 12:30:11 -0700 [thread overview]
Message-ID: <919519d6-855f-4596-a7a1-396446b4cca2@intel.com> (raw)
In-Reply-To: <d8969391-26de-465f-894a-aa75c0947bc5@intel.com>
On 5/8/2025 12:50 PM, Michal Wajdeczko wrote:
> On 08.05.2025 03:34, John.C.Harrison@Intel.com wrote:
>> From: John Harrison <John.C.Harrison@Intel.com>
>>
>> These error codes are not actually used in the driver but it is
>> extremely useful to have them available to understand error messages.
>>
>> v2: Add a bunch more error codes and drop 'status' from names (review
>> feedback by Michal W).
>>
>> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
> Reviewed-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
>
> with one nit below
>
>> ---
>> drivers/gpu/drm/xe/abi/guc_errors_abi.h | 15 ++++++++++++---
>> 1 file changed, 12 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/xe/abi/guc_errors_abi.h b/drivers/gpu/drm/xe/abi/guc_errors_abi.h
>> index 2c627a21648f..cf00300add37 100644
>> --- a/drivers/gpu/drm/xe/abi/guc_errors_abi.h
>> +++ b/drivers/gpu/drm/xe/abi/guc_errors_abi.h
>> @@ -6,8 +6,8 @@
>> #ifndef _ABI_GUC_ERRORS_ABI_H
>> #define _ABI_GUC_ERRORS_ABI_H
>>
>> -enum xe_guc_response_status {
>> - XE_GUC_RESPONSE_STATUS_SUCCESS = 0x0,
>> +enum xe_guc_response {
>> + XE_GUC_RESPONSE_SUCCESS = 0x0,
> this value seems to be some leftover from an earlier GuC ABI where there
> was single H2G RESPONSE message, but today, as we have separate HXG
> RESPONSE SUCCESS and FAILURE message types, there is no place for the
> success code in SUCCESS message and in the FAILURE message we expect
> only error responses, and 0 there can't be treated as success any more
Good point!
> maybe we can put some note here until official spec is fixed?
I'll just drop it. The file does not need to be an exact copy of the
spec, it is just a reference aid for debugging. So no point having
meaningless entries.
John.
>
>> XE_GUC_RESPONSE_ERROR_PROTOCOL = 0x04,
>> XE_GUC_RESPONSE_INVALID_STATE = 0x0A,
>> XE_GUC_RESPONSE_UNSUPPORTED_VERSION = 0x0B,
>> @@ -21,12 +21,20 @@ enum xe_guc_response_status {
>> XE_GUC_RESPONSE_CANNOT_COMPLETE_ACTION = 0x41,
>> XE_GUC_RESPONSE_INVALID_KLV_DATA = 0x50,
>> XE_GUC_RESPONSE_INVALID_PARAMS = 0x60,
>> + XE_GUC_RESPONSE_INVALID_CONTEXT_INDEX = 0x61,
>> + XE_GUC_RESPONSE_INVALID_CONTEXT_REGISTRATION = 0x62,
>> + XE_GUC_RESPONSE_INVALID_DOORBELL_ID = 0x63,
>> + XE_GUC_RESPONSE_INVALID_ENGINE_ID = 0x64,
>> XE_GUC_RESPONSE_INVALID_BUFFER_RANGE = 0x70,
>> XE_GUC_RESPONSE_INVALID_BUFFER = 0x71,
>> + XE_GUC_RESPONSE_BUFFER_ALREADY_REGISTERED = 0x72,
>> XE_GUC_RESPONSE_INVALID_GGTT_ADDRESS = 0x80,
>> XE_GUC_RESPONSE_PENDING_ACTION = 0x90,
>> + XE_GUC_RESPONSE_CONTEXT_NOT_REGISTERED = 0x100,
>> + XE_GUC_RESPONSE_CONTEXT_ALREADY_REGISTERED = 0X101,
>> XE_GUC_RESPONSE_INVALID_SIZE = 0x102,
>> XE_GUC_RESPONSE_MALFORMED_KLV = 0x103,
>> + XE_GUC_RESPONSE_INVALID_CONTEXT = 0x104,
>> XE_GUC_RESPONSE_INVALID_KLV_KEY = 0x105,
>> XE_GUC_RESPONSE_DATA_TOO_LARGE = 0x106,
>> XE_GUC_RESPONSE_VF_MIGRATED = 0x107,
>> @@ -40,10 +48,11 @@ enum xe_guc_response_status {
>> XE_GUC_RESPONSE_CTB_NOT_REGISTERED = 0x304,
>> XE_GUC_RESPONSE_CTB_IN_USE = 0x305,
>> XE_GUC_RESPONSE_CTB_INVALID_DESC = 0x306,
>> + XE_GUC_RESPONSE_HW_TIMEOUT = 0x30C,
>> XE_GUC_RESPONSE_CTB_SOURCE_INVALID_DESCRIPTOR = 0x30D,
>> XE_GUC_RESPONSE_CTB_DESTINATION_INVALID_DESCRIPTOR = 0x30E,
>> XE_GUC_RESPONSE_INVALID_CONFIG_STATE = 0x30F,
>> - XE_GUC_RESPONSE_STATUS_GENERIC_FAIL = 0xF000,
>> + XE_GUC_RESPONSE_GENERIC_FAIL = 0xF000,
>> };
>>
>> enum xe_guc_load_status {
next prev parent reply other threads:[~2025-05-12 19:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 1:34 [PATCH v3 0/4] Track FAST_REQ H2Gs to report where errors came from John.C.Harrison
2025-05-08 1:34 ` [PATCH v3 1/4] drm/xe/guc: Remove double blank line John.C.Harrison
2025-05-08 19:37 ` Michal Wajdeczko
2025-05-08 1:34 ` [PATCH v3 2/4] drm/xe/guc: Add missing H2G error code definitions John.C.Harrison
2025-05-08 19:50 ` Michal Wajdeczko
2025-05-12 19:30 ` John Harrison [this message]
2025-05-08 1:34 ` [PATCH v3 3/4] drm/xe/guc: Rename CONFIG_XE_LARGE_GUC_BUFFER John.C.Harrison
2025-05-08 19:52 ` Michal Wajdeczko
2025-05-08 1:34 ` [PATCH v3 4/4] drm/xe/guc: Track FAST_REQ H2Gs to report where errors came from John.C.Harrison
2025-05-08 20:11 ` Michal Wajdeczko
2025-05-12 19:52 ` John Harrison
2025-05-08 1:40 ` ✓ CI.Patch_applied: success for Track FAST_REQ H2Gs to report where errors came from (rev2) Patchwork
2025-05-08 1:40 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-08 1:41 ` ✓ CI.KUnit: success " Patchwork
2025-05-08 1:50 ` ✓ CI.Build: " Patchwork
2025-05-08 1:52 ` ✓ CI.Hooks: " Patchwork
2025-05-08 1:53 ` ✓ CI.checksparse: " Patchwork
2025-05-08 2:15 ` ✓ Xe.CI.BAT: " Patchwork
2025-05-08 22:58 ` ✗ Xe.CI.Full: failure " Patchwork
2025-05-26 18:39 ` ✗ CI.Patch_applied: " Patchwork
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=919519d6-855f-4596-a7a1-396446b4cca2@intel.com \
--to=john.c.harrison@intel.com \
--cc=Intel-Xe@Lists.FreeDesktop.Org \
--cc=michal.wajdeczko@intel.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