From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [PATCH v2 0/8] PF: Support for adverse events notifications
Date: Tue, 14 May 2024 21:00:07 +0200 [thread overview]
Message-ID: <20240514190015.2172-1-michal.wajdeczko@intel.com> (raw)
The GuC firmware monitors VF's activity and notifies the PF driver
once any configured threshold related to such activity is exceeded.
To avoid having to rewrite a lot of code for each threshold and to
be prepared for any new GuC threshold additions, where possible,
use macros to generate threshold specific code.
v1: https://patchwork.freedesktop.org/series/133236/#rev1
v2: improve readability of macros (Piotr)
fix kernel-doc (Piotr, CI.hooks)
add explicit asserts (Piotr)
Michal Wajdeczko (8):
drm/xe/guc: Add more KLV helper macros
drm/xe/guc: Introduce GuC KLV thresholds set
drm/xe/guc: Add support for threshold KLVs in to_string() helper
drm/xe/pf: Introduce functions to configure VF thresholds
drm/xe/pf: Allow configuration of VF thresholds over debugfs
drm/xe/guc: Add GUC2PF_ADVERSE_EVENT to ABI
drm/xe/pf: Track adverse events notifications from GuC
drm/xe/pf: Expose PF monitor details via debugfs
drivers/gpu/drm/xe/Makefile | 1 +
.../gpu/drm/xe/abi/guc_actions_sriov_abi.h | 30 ++++
drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c | 87 +++++++++++
drivers/gpu/drm/xe/xe_gt_sriov_pf_config.h | 6 +
.../gpu/drm/xe/xe_gt_sriov_pf_config_types.h | 4 +
drivers/gpu/drm/xe/xe_gt_sriov_pf_debugfs.c | 79 ++++++++++
drivers/gpu/drm/xe/xe_gt_sriov_pf_monitor.c | 147 ++++++++++++++++++
drivers/gpu/drm/xe/xe_gt_sriov_pf_monitor.h | 27 ++++
.../gpu/drm/xe/xe_gt_sriov_pf_monitor_types.h | 22 +++
drivers/gpu/drm/xe/xe_gt_sriov_pf_types.h | 5 +
drivers/gpu/drm/xe/xe_guc_ct.c | 4 +
drivers/gpu/drm/xe/xe_guc_klv_helpers.c | 12 ++
drivers/gpu/drm/xe/xe_guc_klv_helpers.h | 15 +-
.../gpu/drm/xe/xe_guc_klv_thresholds_set.h | 64 ++++++++
.../drm/xe/xe_guc_klv_thresholds_set_types.h | 68 ++++++++
15 files changed, 570 insertions(+), 1 deletion(-)
create mode 100644 drivers/gpu/drm/xe/xe_gt_sriov_pf_monitor.c
create mode 100644 drivers/gpu/drm/xe/xe_gt_sriov_pf_monitor.h
create mode 100644 drivers/gpu/drm/xe/xe_gt_sriov_pf_monitor_types.h
create mode 100644 drivers/gpu/drm/xe/xe_guc_klv_thresholds_set.h
create mode 100644 drivers/gpu/drm/xe/xe_guc_klv_thresholds_set_types.h
--
2.43.0
next reply other threads:[~2024-05-14 19:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 19:00 Michal Wajdeczko [this message]
2024-05-14 19:00 ` [PATCH v2 1/8] drm/xe/guc: Add more KLV helper macros Michal Wajdeczko
2024-05-14 19:00 ` [PATCH v2 2/8] drm/xe/guc: Introduce GuC KLV thresholds set Michal Wajdeczko
2024-05-16 14:23 ` Lucas De Marchi
2024-05-16 14:51 ` Michal Wajdeczko
2024-05-14 19:00 ` [PATCH v2 3/8] drm/xe/guc: Add support for threshold KLVs in to_string() helper Michal Wajdeczko
2024-05-14 19:00 ` [PATCH v2 4/8] drm/xe/pf: Introduce functions to configure VF thresholds Michal Wajdeczko
2024-05-14 19:00 ` [PATCH v2 5/8] drm/xe/pf: Allow configuration of VF thresholds over debugfs Michal Wajdeczko
2024-05-14 19:00 ` [PATCH v2 6/8] drm/xe/guc: Add GUC2PF_ADVERSE_EVENT to ABI Michal Wajdeczko
2024-05-14 19:00 ` [PATCH v2 7/8] drm/xe/pf: Track adverse events notifications from GuC Michal Wajdeczko
2024-05-14 19:00 ` [PATCH v2 8/8] drm/xe/pf: Expose PF monitor details via debugfs Michal Wajdeczko
2024-05-14 19:06 ` ✓ CI.Patch_applied: success for PF: Support for adverse events notifications (rev2) Patchwork
2024-05-14 19:06 ` ✗ CI.checkpatch: warning " Patchwork
2024-05-14 19:07 ` ✓ CI.KUnit: success " Patchwork
2024-05-14 19:19 ` ✓ CI.Build: " Patchwork
2024-05-14 19:21 ` ✓ CI.Hooks: " Patchwork
2024-05-14 19:23 ` ✓ CI.checksparse: " Patchwork
2024-05-14 19:45 ` ✓ CI.BAT: " Patchwork
2024-05-14 20:44 ` ✗ CI.FULL: failure " Patchwork
2024-05-15 11:54 ` 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=20240514190015.2172-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