From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [PATCH 3/7] drm/xe/guc: Add GUC2PF_ADVERSE_EVENT to ABI
Date: Thu, 28 Mar 2024 19:31:43 +0100 [thread overview]
Message-ID: <20240328183147.495-4-michal.wajdeczko@intel.com> (raw)
In-Reply-To: <20240328183147.495-1-michal.wajdeczko@intel.com>
In upcoming patches the PF driver will add support to configure
monitoring of the VFs activities and will must be abel to handle
related GUC2PF_ADVERSE_EVENT event messages from the GuC.
Add necessary definitions to our GuC firmware ABI header.
Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
---
.../gpu/drm/xe/abi/guc_actions_sriov_abi.h | 30 +++++++++++++++++++
1 file changed, 30 insertions(+)
diff --git a/drivers/gpu/drm/xe/abi/guc_actions_sriov_abi.h b/drivers/gpu/drm/xe/abi/guc_actions_sriov_abi.h
index 561c54a86016..ea01b21afe28 100644
--- a/drivers/gpu/drm/xe/abi/guc_actions_sriov_abi.h
+++ b/drivers/gpu/drm/xe/abi/guc_actions_sriov_abi.h
@@ -171,6 +171,36 @@
#define VF2GUC_RELAY_TO_PF_REQUEST_MSG_n_RELAY_DATAx GUC_HXG_REQUEST_MSG_n_DATAn
#define VF2GUC_RELAY_TO_PF_REQUEST_MSG_NUM_RELAY_DATA GUC_RELAY_MSG_MAX_LEN
+/**
+ * DOC: GUC2PF_ADVERSE_EVENT
+ *
+ * This message is used by the GuC to notify PF about adverse events.
+ *
+ * This G2H message must be sent as `CTB HXG Message`_.
+ *
+ * +---+-------+--------------------------------------------------------------+
+ * | | Bits | Description |
+ * +===+=======+==============================================================+
+ * | 0 | 31 | ORIGIN = GUC_HXG_ORIGIN_GUC_ |
+ * | +-------+--------------------------------------------------------------+
+ * | | 30:28 | TYPE = GUC_HXG_TYPE_EVENT_ |
+ * | +-------+--------------------------------------------------------------+
+ * | | 27:16 | DATA0 = MBZ |
+ * | +-------+--------------------------------------------------------------+
+ * | | 15:0 | ACTION = _`GUC_ACTION_GUC2PF_ADVERSE_EVENT` = 0x5104 |
+ * +---+-------+--------------------------------------------------------------+
+ * | 1 | 31:0 | DATA1 = **VFID** - VF identifier |
+ * +---+-------+--------------------------------------------------------------+
+ * | 2 | 31:0 | DATA2 = **THRESHOLD** - key of the exceeded threshold |
+ * +---+-------+--------------------------------------------------------------+
+ */
+#define GUC_ACTION_GUC2PF_ADVERSE_EVENT 0x5104
+
+#define GUC2PF_ADVERSE_EVENT_EVENT_MSG_LEN (GUC_HXG_EVENT_MSG_MIN_LEN + 2u)
+#define GUC2PF_ADVERSE_EVENT_EVENT_MSG_0_MBZ GUC_HXG_EVENT_MSG_0_DATA0
+#define GUC2PF_ADVERSE_EVENT_EVENT_MSG_1_VFID GUC_HXG_EVENT_MSG_n_DATAn
+#define GUC2PF_ADVERSE_EVENT_EVENT_MSG_2_THRESHOLD GUC_HXG_EVENT_MSG_n_DATAn
+
/**
* DOC: GUC2PF_VF_STATE_NOTIFY
*
--
2.43.0
next prev parent reply other threads:[~2024-03-28 18:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 18:31 [PATCH 0/7] Update GuC ABI definitions Michal Wajdeczko
2024-03-28 18:31 ` [PATCH 1/7] drm/xe/guc: Add PF2GUC_UPDATE_VF_CFG to ABI Michal Wajdeczko
2024-03-28 18:31 ` [PATCH 2/7] drm/xe/guc: Add PF2GUC_UPDATE_VGT_POLICY " Michal Wajdeczko
2024-03-28 18:31 ` Michal Wajdeczko [this message]
2024-03-28 18:31 ` [PATCH 4/7] drm/xe/guc: Add VF2GUC_MATCH_VERSION " Michal Wajdeczko
2024-03-28 18:31 ` [PATCH 5/7] drm/xe/guc: Add VF2GUC_VF_RESET " Michal Wajdeczko
2024-03-28 18:31 ` [PATCH 6/7] drm/xe/guc: Add VF2GUC_QUERY_SINGLE_KLV " Michal Wajdeczko
2024-03-28 18:31 ` [PATCH 7/7] drm/xe/guc: Add GLOBAL_CFG_GMD_ID KLV definition Michal Wajdeczko
2024-03-29 2:58 ` ✓ CI.Patch_applied: success for Update GuC ABI definitions Patchwork
2024-03-29 2:59 ` ✗ CI.checkpatch: warning " Patchwork
2024-03-29 3:00 ` ✓ CI.KUnit: success " Patchwork
2024-03-29 3:11 ` ✓ CI.Build: " Patchwork
2024-03-29 3:13 ` ✓ CI.Hooks: " Patchwork
2024-03-29 3:15 ` ✓ CI.checksparse: " Patchwork
2024-03-29 3:50 ` ✓ CI.BAT: " Patchwork
2024-03-29 16:14 ` [PATCH 0/7] " Lucas De Marchi
2024-03-29 16:50 ` Michal Wajdeczko
2024-04-01 12:54 ` Lucas De Marchi
2024-04-04 1:10 ` John Harrison
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=20240328183147.495-4-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