Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [PATCH 0/3] PF: Expose GT-level SR-IOV details over debugfs
Date: Thu, 18 Apr 2024 22:34:39 +0200	[thread overview]
Message-ID: <20240418203442.226-1-michal.wajdeczko@intel.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 1321 bytes --]

   /sys/kernel/debug/dri/0/
   +-- gt0
   ¦   +-- pf
   ¦   ¦   +-- contexts_provisioned
   ¦   ¦   +-- contexts_spare
   ¦   ¦   +-- doorbells_provisioned
   ¦   ¦   +-- doorbells_spare
   ¦   ¦   +-- exec_quantum_ms
   ¦   ¦   +-- ggtt_available
   ¦   ¦   +-- ggtt_provisioned
   ¦   ¦   +-- ggtt_spare
   ¦   ¦   +-- lmem_spare
   ¦   ¦   +-- preempt_timeout_us
   ¦   ¦   +-- reset_engine
   ¦   ¦   +-- sample_period_ms
   ¦   ¦   +-- sched_if_idle
   ¦   +-- vf1
   ¦   ¦   +-- contexts_quota
   ¦   ¦   +-- control
   ¦   ¦   +-- doorbells_quota
   ¦   ¦   +-- exec_quantum_ms
   ¦   ¦   +-- ggtt_quota
   ¦   ¦   +-- lmem_quota
   ¦   ¦   +-- preempt_timeout_us

Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>

Michal Wajdeczko (3):
  drm/xe/pf: Expose SR-IOV VFs configuration over debugfs
  drm/xe/pf: Expose SR-IOV VF control commands over debugfs
  drm/xe/pf: Expose SR-IOV policy settings over debugfs

 drivers/gpu/drm/xe/Makefile                 |   1 +
 drivers/gpu/drm/xe/xe_gt_debugfs.c          |   5 +
 drivers/gpu/drm/xe/xe_gt_sriov_pf_debugfs.c | 332 ++++++++++++++++++++
 drivers/gpu/drm/xe/xe_gt_sriov_pf_debugfs.h |  18 ++
 4 files changed, 356 insertions(+)
 create mode 100644 drivers/gpu/drm/xe/xe_gt_sriov_pf_debugfs.c
 create mode 100644 drivers/gpu/drm/xe/xe_gt_sriov_pf_debugfs.h

-- 
2.43.0


             reply	other threads:[~2024-04-18 20:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-18 20:34 Michal Wajdeczko [this message]
2024-04-18 20:34 ` [PATCH 1/3] drm/xe/pf: Expose SR-IOV VFs configuration over debugfs Michal Wajdeczko
2024-04-22 16:43   ` Piotr Piórkowski
2024-04-22 17:12     ` Michal Wajdeczko
2024-04-18 20:34 ` [PATCH 2/3] drm/xe/pf: Expose SR-IOV VF control commands " Michal Wajdeczko
2024-04-22 16:55   ` Piotr Piórkowski
2024-04-18 20:34 ` [PATCH 3/3] drm/xe/pf: Expose SR-IOV policy settings " Michal Wajdeczko
2024-04-22 17:02   ` Piotr Piórkowski
2024-04-22 17:24     ` Michal Wajdeczko
2024-04-22 19:39   ` Rodrigo Vivi
2024-04-22 20:05     ` Michal Wajdeczko
2024-04-22 20:28       ` Rodrigo Vivi
2024-04-18 22:24 ` ✓ CI.Patch_applied: success for series starting with [1/3] drm/xe/pf: Expose SR-IOV VFs configuration " Patchwork
2024-04-18 22:24 ` ✗ CI.checkpatch: warning " Patchwork
2024-04-18 22:27 ` ✓ CI.KUnit: success " Patchwork
2024-04-18 22:39 ` ✓ CI.Build: " Patchwork
2024-04-18 22:43 ` ✓ CI.Hooks: " Patchwork
2024-04-18 22:44 ` ✓ CI.checksparse: " Patchwork
2024-04-18 23:40 ` ✓ CI.BAT: " Patchwork
2024-04-20 16:05 ` ✗ CI.FULL: failure " 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=20240418203442.226-1-michal.wajdeczko@intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=rodrigo.vivi@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