From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Matthew Brost <matthew.brost@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/xe/guc: Fix arguments passed to relay G2H handlers
Date: Thu, 11 Jan 2024 10:37:31 +0100 [thread overview]
Message-ID: <b249c605-25f7-42d7-b5e4-ed2fc59a51f0@intel.com> (raw)
In-Reply-To: <ZZ8jSw7WdvokR5Rh@DUT025-TGLU.fm.intel.com>
On 11.01.2024 00:07, Matthew Brost wrote:
> On Wed, Jan 10, 2024 at 08:59:51PM +0100, Michal Wajdeczko wrote:
>> By default CT code was passing just payload of the G2H event
>> message, while Relay code expects full G2H message including
>> HXG header which contains DATA0 field. Fix that.
>>
>> Fixes: 152577060697 ("drm/xe/guc: Start handling GuC Relay event messages")
>> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
>
> FWIW I do think the argument names in xe_guc_relay_process_* functions
> should be changed but not going to hold of this fix.
I can rename message argument in relay g2h handlers to "hxg", but what
about the other g2h handlers, which (IMO wrongly) take just payload, not
a message, while still use "msg" as an argument name:
int xe_guc_sched_done_handler(... u32 *msg, u32 len)
int xe_guc_deregister_done_handler(... u32 *msg, u32 len)
int xe_guc_exec_queue_reset_handler(... u32 *msg, u32 len)
int xe_guc_exec_queue_memory_cat_error_handler(... u32 *msg, u32 len)
int xe_guc_exec_queue_reset_failure_handler(... u32 *msg, u32 len)
int xe_guc_pagefault_handler(... u32 *msg, u32 len)
int xe_guc_tlb_invalidation_done_handler(... u32 *msg, u32 len)
int xe_guc_access_counter_notify_handler(... u32 *msg, u32 len)
>
> With that:
> Reviewed-by: Matthew Brost <matthew.brost@intel.com>
>
>> ---
>> drivers/gpu/drm/xe/xe_guc_ct.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_guc_ct.c b/drivers/gpu/drm/xe/xe_guc_ct.c
>> index d6b7020a2d2f..4a0c9ce13bf8 100644
>> --- a/drivers/gpu/drm/xe/xe_guc_ct.c
>> +++ b/drivers/gpu/drm/xe/xe_guc_ct.c
>> @@ -984,10 +984,10 @@ static int process_g2h_msg(struct xe_guc_ct *ct, u32 *msg, u32 len)
>> adj_len);
>> break;
>> case XE_GUC_ACTION_GUC2PF_RELAY_FROM_VF:
>> - ret = xe_guc_relay_process_guc2pf(&guc->relay, payload, adj_len);
>> + ret = xe_guc_relay_process_guc2pf(&guc->relay, hxg, hxg_len);
>> break;
>> case XE_GUC_ACTION_GUC2VF_RELAY_FROM_PF:
>> - ret = xe_guc_relay_process_guc2vf(&guc->relay, payload, adj_len);
>> + ret = xe_guc_relay_process_guc2vf(&guc->relay, hxg, hxg_len);
>> break;
>> default:
>> drm_err(&xe->drm, "unexpected action 0x%04x\n", action);
>> --
>> 2.25.1
>>
next prev parent reply other threads:[~2024-01-11 9:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 19:59 [PATCH 1/2] drm/xe/guc: Use HXG definitions on HXG messages Michal Wajdeczko
2024-01-10 19:59 ` [PATCH 2/2] drm/xe/guc: Fix arguments passed to relay G2H handlers Michal Wajdeczko
2024-01-10 23:07 ` Matthew Brost
2024-01-11 9:37 ` Michal Wajdeczko [this message]
2024-01-11 20:08 ` Matthew Brost
2024-01-11 21:00 ` Michal Wajdeczko
2024-01-10 23:06 ` [PATCH 1/2] drm/xe/guc: Use HXG definitions on HXG messages Matthew Brost
2024-01-11 9:44 ` Michal Wajdeczko
2024-01-11 1:01 ` ✓ CI.Patch_applied: success for series starting with [1/2] " Patchwork
2024-01-11 1:02 ` ✗ CI.checkpatch: warning " Patchwork
2024-01-11 1:02 ` ✓ CI.KUnit: success " Patchwork
2024-01-11 1:10 ` ✓ CI.Build: " Patchwork
2024-01-11 1:10 ` ✓ CI.Hooks: " Patchwork
2024-01-11 1:12 ` ✓ CI.checksparse: " Patchwork
2024-01-11 1:48 ` ✓ CI.BAT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2024-01-09 23:00 [PATCH 1/2] drm/xe/guc: Use proper definitions while processing G2H events Michal Wajdeczko
2024-01-09 23:00 ` [PATCH 2/2] drm/xe/guc: Fix arguments passed to relay G2H handlers Michal Wajdeczko
2024-01-10 0:47 ` Matthew Brost
2024-01-10 17:55 ` Michal Wajdeczko
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=b249c605-25f7-42d7-b5e4-ed2fc59a51f0@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@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