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>,
"Piotr Piórkowski" <piotr.piorkowski@intel.com>,
"Satyanarayana K V P" <satyanarayana.k.v.p@intel.com>
Subject: [PATCH 0/5] drm/xe/configfs: Add sriov.admin_only_pf attribute
Date: Wed, 21 Jan 2026 22:42:11 +0100 [thread overview]
Message-ID: <20260121214218.2817-1-michal.wajdeczko@intel.com> (raw)
Currently we are relying on the info.probe_display flag to guess if maybe
we should provision single VF in more favorable way, without reserving
too much resources for the PF (mode known as 'admin-only-PF').
Start using configfs to allow flexible admin-only-PF configuration based
on the real need. But before that, do some cleanups and preparations.
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Matthew Brost <matthew.brost@intel.com>
Cc: Piotr Piórkowski <piotr.piorkowski@intel.com>
Cc: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
Michal Wajdeczko (5):
drm/xe: Keep all defaults in single header
drm/xe/configfs: Use proper notation for local include
drm/xe/configfs: Always return consistent max_vfs value
drm/xe/pf: Define admin_only as real flag
drm/xe/configfs: Add sriov.admin_only_pf attribute
drivers/gpu/drm/xe/xe_configfs.c | 64 +++++++++++++++++++++++-
drivers/gpu/drm/xe/xe_configfs.h | 16 +++++-
drivers/gpu/drm/xe/xe_defaults.h | 26 ++++++++++
drivers/gpu/drm/xe/xe_device.c | 3 +-
drivers/gpu/drm/xe/xe_device_types.h | 3 --
drivers/gpu/drm/xe/xe_module.c | 42 ++++++----------
drivers/gpu/drm/xe/xe_sriov_pf.c | 10 ++--
drivers/gpu/drm/xe/xe_sriov_pf_helpers.h | 3 +-
drivers/gpu/drm/xe/xe_sriov_pf_types.h | 3 ++
9 files changed, 131 insertions(+), 39 deletions(-)
create mode 100644 drivers/gpu/drm/xe/xe_defaults.h
--
2.47.1
next reply other threads:[~2026-01-21 21:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 21:42 Michal Wajdeczko [this message]
2026-01-21 21:42 ` [PATCH 1/5] drm/xe: Keep all defaults in single header Michal Wajdeczko
2026-01-23 10:29 ` Piotr Piórkowski
2026-02-03 0:11 ` Rodrigo Vivi
2026-02-03 11:13 ` Jani Nikula
2026-02-03 14:58 ` Michal Wajdeczko
2026-01-21 21:42 ` [PATCH 2/5] drm/xe/configfs: Use proper notation for local include Michal Wajdeczko
2026-01-23 10:29 ` Piotr Piórkowski
2026-01-21 21:42 ` [PATCH 3/5] drm/xe/configfs: Always return consistent max_vfs value Michal Wajdeczko
2026-01-28 15:51 ` Piotr Piórkowski
2026-01-21 21:42 ` [PATCH 4/5] drm/xe/pf: Define admin_only as real flag Michal Wajdeczko
2026-01-27 21:05 ` [PATCH v2 " Michal Wajdeczko
2026-01-28 15:56 ` Piotr Piórkowski
2026-01-21 21:42 ` [PATCH 5/5] drm/xe/configfs: Add sriov.admin_only_pf attribute Michal Wajdeczko
2026-01-28 16:35 ` Piotr Piórkowski
2026-01-28 23:42 ` Michal Wajdeczko
2026-01-21 22:25 ` ✗ CI.checkpatch: warning for " Patchwork
2026-01-21 22:26 ` ✗ CI.KUnit: failure " Patchwork
2026-01-27 21:34 ` ✗ CI.checkpatch: warning for drm/xe/configfs: Add sriov.admin_only_pf attribute (rev2) Patchwork
2026-01-27 21:35 ` ✓ CI.KUnit: success " Patchwork
2026-01-27 22:33 ` ✓ Xe.CI.BAT: " Patchwork
2026-01-28 6:46 ` ✓ Xe.CI.Full: " 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=20260121214218.2817-1-michal.wajdeczko@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
--cc=piotr.piorkowski@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=satyanarayana.k.v.p@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