From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [PATCH] drm/xe/guc: Fix arguments passed to relay G2H handlers
Date: Fri, 19 Apr 2024 17:03:51 +0200 [thread overview]
Message-ID: <20240419150351.358-1-michal.wajdeczko@intel.com> (raw)
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: 26d4481ac23f ("drm/xe/guc: Start handling GuC Relay event messages")
Signed-off-by: Michal Wajdeczko <michal.wajdeczko@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 ac9324338ccf..8ac819a7061e 100644
--- a/drivers/gpu/drm/xe/xe_guc_ct.c
+++ b/drivers/gpu/drm/xe/xe_guc_ct.c
@@ -1058,10 +1058,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;
case GUC_ACTION_GUC2PF_VF_STATE_NOTIFY:
ret = xe_gt_sriov_pf_control_process_guc2pf(gt, hxg, hxg_len);
--
2.43.0
next reply other threads:[~2024-04-19 15:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 15:03 Michal Wajdeczko [this message]
2024-04-19 22:49 ` ✓ CI.Patch_applied: success for drm/xe/guc: Fix arguments passed to relay G2H handlers Patchwork
2024-04-19 22:49 ` ✓ CI.checkpatch: " Patchwork
2024-04-19 22:55 ` ✓ CI.KUnit: " Patchwork
2024-04-19 23:07 ` ✓ CI.Build: " Patchwork
2024-04-19 23:14 ` ✓ CI.Hooks: " Patchwork
2024-04-19 23:15 ` ✓ CI.checksparse: " Patchwork
2024-04-19 23:41 ` ✗ CI.BAT: failure " Patchwork
2024-04-22 17:28 ` Michal Wajdeczko
2024-04-20 17:33 ` ✓ CI.Patch_applied: success for drm/xe/guc: Fix arguments passed to relay G2H handlers (rev2) Patchwork
2024-04-20 17:33 ` ✓ CI.checkpatch: " Patchwork
2024-04-20 17:34 ` ✓ CI.KUnit: " Patchwork
2024-04-20 17:53 ` ✓ CI.Build: " Patchwork
2024-04-20 18:11 ` ✓ CI.Hooks: " Patchwork
2024-04-20 18:18 ` ✓ CI.checksparse: " Patchwork
2024-04-21 17:04 ` ✓ CI.FULL: success for drm/xe/guc: Fix arguments passed to relay G2H handlers Patchwork
2024-04-22 17:11 ` [PATCH] " Piotr Piórkowski
2024-04-23 13:47 ` ✗ CI.Patch_applied: failure for drm/xe/guc: Fix arguments passed to relay G2H handlers (rev3) 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=20240419150351.358-1-michal.wajdeczko@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-xe@lists.freedesktop.org \
/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