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>,
Matthew Brost <matthew.brost@intel.com>
Subject: [PATCH 0/9] drm/xe/pf: Allow to change VFs VRAM quota using sysfs
Date: Sun, 15 Feb 2026 21:33:14 +0100 [thread overview]
Message-ID: <20260215203323.595-1-michal.wajdeczko@intel.com> (raw)
Extend Xe driver specific sysfs SR-IOV knobs with VRAM provisioning.
/sys/bus/pci/drivers/xe/BDF/
├── sriov_admin/
├── .bulk_profile
│ └── vram_quota [RW] unsigned integer
├── vf1/
│ └── profile
│ └── vram_quota [RW] unsigned integer
├── vf2/
│ └── profile
│ └── vram_quota [RW] unsigned integer
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Matthew Brost <matthew.brost@intel.com>
Michal Wajdeczko (9):
drm/xe/pf: Add locked variants of VRAM configuration functions
drm/xe/pf: Add functions for VRAM provisioning
drm/xe/pf: Allow to change VFs VRAM quota using sysfs
drm/xe/pf: Use migration-friendly VRAM auto-provisioning
drm/xe/tests: Add KUnit tests for new VRAM fair provisioning
drm/xe/pf: Don't check for empty config
drm/xe/pf: Prefer guard(mutex) when doing fair LMEM provisioning
drm/xe/pf: Skip VRAM auto-provisioning if already provisioned
drm/xe/pf: Add documentation for vram_quota
.../ABI/testing/sysfs-driver-intel-xe-sriov | 31 ++++
.../xe/tests/xe_gt_sriov_pf_config_kunit.c | 90 +++++++++-
drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c | 167 ++++++++++++++++--
drivers/gpu/drm/xe/xe_gt_sriov_pf_config.h | 4 +
drivers/gpu/drm/xe/xe_sriov_pf_provision.c | 121 +++++++++++--
drivers/gpu/drm/xe/xe_sriov_pf_provision.h | 4 +
drivers/gpu/drm/xe/xe_sriov_pf_sysfs.c | 26 ++-
7 files changed, 416 insertions(+), 27 deletions(-)
--
2.47.1
next reply other threads:[~2026-02-15 20:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-15 20:33 Michal Wajdeczko [this message]
2026-02-15 20:33 ` [PATCH 1/9] drm/xe/pf: Add locked variants of VRAM configuration functions Michal Wajdeczko
2026-02-16 14:37 ` Piotr Piórkowski
2026-02-15 20:33 ` [PATCH 2/9] drm/xe/pf: Add functions for VRAM provisioning Michal Wajdeczko
2026-02-16 15:02 ` Piotr Piórkowski
2026-02-16 15:11 ` Piotr Piórkowski
2026-02-15 20:33 ` [PATCH 3/9] drm/xe/pf: Allow to change VFs VRAM quota using sysfs Michal Wajdeczko
2026-02-16 15:29 ` Piotr Piórkowski
2026-02-18 21:07 ` Rodrigo Vivi
2026-02-15 20:33 ` [PATCH 4/9] drm/xe/pf: Use migration-friendly VRAM auto-provisioning Michal Wajdeczko
2026-02-16 16:14 ` Piotr Piórkowski
2026-02-15 20:33 ` [PATCH 5/9] drm/xe/tests: Add KUnit tests for new VRAM fair provisioning Michal Wajdeczko
2026-02-16 16:23 ` Piotr Piórkowski
2026-02-15 20:33 ` [PATCH 6/9] drm/xe/pf: Don't check for empty config Michal Wajdeczko
2026-02-16 16:27 ` Piotr Piórkowski
2026-02-15 20:33 ` [PATCH 7/9] drm/xe/pf: Prefer guard(mutex) when doing fair LMEM provisioning Michal Wajdeczko
2026-02-16 16:36 ` Piotr Piórkowski
2026-02-15 20:33 ` [PATCH 8/9] drm/xe/pf: Skip VRAM auto-provisioning if already provisioned Michal Wajdeczko
2026-02-16 16:59 ` Piotr Piórkowski
2026-02-15 20:33 ` [PATCH 9/9] drm/xe/pf: Add documentation for vram_quota Michal Wajdeczko
2026-02-16 17:04 ` Piotr Piórkowski
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=20260215203323.595-1-michal.wajdeczko@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
--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