From: Nareshkumar Gollakoti <naresh.kumar.g@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: naresh.kumar.g@intel.com, Michal.Wajdeczko@intel.com
Subject: [PATCH v3 0/2] drm/xe:Mutual exclusivity between CCS-mode and PF
Date: Mon, 2 Feb 2026 22:38:11 +0530 [thread overview]
Message-ID: <20260202170810.1393147-4-naresh.kumar.g@intel.com> (raw)
Due to SLA agreement between PF and VFs, Currently we block CCS mode
changes if driver is running as PF, even if there are no VFs enabled yet.
Use lockdown mechanism provided by the PF to relax that limitation
and still enforce above VFs related requirements.Also skipping CCS-mode
sysfs entry in VF Mode.
---
The previous change log can be referenced at the following link,
https://patchwork.freedesktop.org/series/154538/#rev9
v1:(Michal)
- Split into two patches with cover letter and subject of cover letter
refactored
v2:(Michal)
- Add direct code instead of gt_prepare_ccs_mode_enabling and
gt_finish_ccs_mode_enabling function's for readability
v3: (Michal)
- Remove Fix up tag in commit message
- Refactored Commit Message
Nareshkumar Gollakoti (2):
drm/xe: Fix Prevent VFs from exposing the CCS mode sysfs file
drm/xe: Mutual exclusivity between CCS-mode and PF
drivers/gpu/drm/xe/xe_gt_ccs_mode.c | 44 +++++++++++++++++++----------
1 file changed, 29 insertions(+), 15 deletions(-)
--
2.43.0
next reply other threads:[~2026-02-02 17:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 17:08 Nareshkumar Gollakoti [this message]
2026-02-02 17:08 ` [PATCH v3 1/2] drm/xe: Fix Prevent VFs from exposing the CCS mode sysfs file Nareshkumar Gollakoti
2026-02-02 17:08 ` [PATCH v3 2/2] drm/xe: Mutual exclusivity between CCS-mode and PF Nareshkumar Gollakoti
2026-02-03 3:51 ` ✓ CI.KUnit: success for drm/xe:Mutual exclusivity between CCS-mode and PF (rev3) Patchwork
2026-02-03 4:30 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-03 16:25 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-02-05 21:10 ` [PATCH v3 0/2] drm/xe:Mutual exclusivity between CCS-mode and PF 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=20260202170810.1393147-4-naresh.kumar.g@intel.com \
--to=naresh.kumar.g@intel.com \
--cc=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