From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
Subject: [PATCH 4/5] drm/xe/pf: Allow to control scheduling priority using debugfs
Date: Thu, 24 Oct 2024 01:11:51 +0200 [thread overview]
Message-ID: <20241023231152.1815-5-michal.wajdeczko@intel.com> (raw)
In-Reply-To: <20241023231152.1815-1-michal.wajdeczko@intel.com>
Add 'priority' attribute that represents the scheduling prority
of the VF or PF. Values {0,1,2} represents {LOW,NORMAL,HIGH}.
Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
---
drivers/gpu/drm/xe/xe_gt_sriov_pf_debugfs.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/drivers/gpu/drm/xe/xe_gt_sriov_pf_debugfs.c b/drivers/gpu/drm/xe/xe_gt_sriov_pf_debugfs.c
index 05df4ab3514b..0b7c78fb18cd 100644
--- a/drivers/gpu/drm/xe/xe_gt_sriov_pf_debugfs.c
+++ b/drivers/gpu/drm/xe/xe_gt_sriov_pf_debugfs.c
@@ -164,6 +164,7 @@ static void pf_add_policy_attrs(struct xe_gt *gt, struct dentry *parent)
* │ │ ├── contexts_spare
* │ │ ├── exec_quantum_ms
* │ │ ├── preempt_timeout_us
+ * │ │ ├── priority
* │ ├── vf1
* │ │ ├── ggtt_quota
* │ │ ├── lmem_quota
@@ -171,6 +172,7 @@ static void pf_add_policy_attrs(struct xe_gt *gt, struct dentry *parent)
* │ │ ├── contexts_quota
* │ │ ├── exec_quantum_ms
* │ │ ├── preempt_timeout_us
+ * │ │ ├── priority
*/
#define DEFINE_SRIOV_GT_CONFIG_DEBUGFS_ATTRIBUTE(CONFIG, TYPE, FORMAT) \
@@ -209,6 +211,7 @@ DEFINE_SRIOV_GT_CONFIG_DEBUGFS_ATTRIBUTE(ctxs, u32, "%llu\n");
DEFINE_SRIOV_GT_CONFIG_DEBUGFS_ATTRIBUTE(dbs, u32, "%llu\n");
DEFINE_SRIOV_GT_CONFIG_DEBUGFS_ATTRIBUTE(exec_quantum, u32, "%llu\n");
DEFINE_SRIOV_GT_CONFIG_DEBUGFS_ATTRIBUTE(preempt_timeout, u32, "%llu\n");
+DEFINE_SRIOV_GT_CONFIG_DEBUGFS_ATTRIBUTE(priority, u32, "%llu\n");
/*
* /sys/kernel/debug/dri/0/
@@ -295,6 +298,8 @@ static void pf_add_config_attrs(struct xe_gt *gt, struct dentry *parent, unsigne
&exec_quantum_fops);
debugfs_create_file_unsafe("preempt_timeout_us", 0644, parent, parent,
&preempt_timeout_fops);
+ debugfs_create_file_unsafe("priority", 0644, parent, parent,
+ &priority_fops);
/* register all threshold attributes */
#define register_threshold_attribute(TAG, NAME, ...) \
--
2.43.0
next prev parent reply other threads:[~2024-10-23 23:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 23:11 [PATCH 0/5] PF: Add support for VF scheduling priority Michal Wajdeczko
2024-10-23 23:11 ` [PATCH 1/5] drm/xe/guc: Add VF_CFG_SCHED_PRIORITY_KEY KLV definition Michal Wajdeczko
2024-10-28 15:34 ` Laguna, Lukasz
2024-10-23 23:11 ` [PATCH 2/5] drm/xe/guc: Add VF_CFG_SCHED_PRIORITY to KLV helper Michal Wajdeczko
2024-10-23 23:11 ` [PATCH 3/5] drm/xe/pf: Add functions to configure VF scheduling priority Michal Wajdeczko
2024-10-23 23:11 ` Michal Wajdeczko [this message]
2024-10-23 23:11 ` [PATCH 5/5] drm/xe/pf: Adjust scheduling priority based on policy change Michal Wajdeczko
2024-10-24 15:30 ` ✓ CI.Patch_applied: success for PF: Add support for VF scheduling priority Patchwork
2024-10-24 15:30 ` ✓ CI.checkpatch: " Patchwork
2024-10-24 15:31 ` ✓ CI.KUnit: " Patchwork
2024-10-24 15:43 ` ✓ CI.Build: " Patchwork
2024-10-24 15:45 ` ✓ CI.Hooks: " Patchwork
2024-10-24 15:46 ` ✓ CI.checksparse: " Patchwork
2024-10-24 16:12 ` ✗ CI.BAT: failure " Patchwork
2024-10-25 18:37 ` ✗ CI.FULL: " Patchwork
2024-10-28 15:51 ` [PATCH 0/5] " Laguna, Lukasz
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=20241023231152.1815-5-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