From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Nareshkumar Gollakoti <naresh.kumar.g@intel.com>,
<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v2 2/2] drm/xe: Mutual exclusivity between CCS-mode and PF
Date: Thu, 29 Jan 2026 22:41:28 +0100 [thread overview]
Message-ID: <8bf19afa-44ab-458b-9cb7-178cfb8d0373@intel.com> (raw)
In-Reply-To: <20260129172246.1106097-6-naresh.kumar.g@intel.com>
On 1/29/2026 6:22 PM, Nareshkumar Gollakoti wrote:
> Due to SLA agreement between PF and VFs,the alternate CCS-mode
^
nit: missing space
> cannot be changed when VFs are already enabled.
> Similarly, enabling VFs is not permitted when the alternate
> CCS-mode is active.
maybe it's worth to mention:
"Currently we block CCS mode changes if driver is running as PF,
even if there are no VFs enabled yet."
above says "why" but what about "how" ? maybe:
"Use lockdown mechanism provided by the PF to relax that limitation
and still enforce above VFs related requirements."
>
> Signed-off-by: Nareshkumar Gollakoti <naresh.kumar.g@intel.com>
> ---
> drivers/gpu/drm/xe/xe_gt_ccs_mode.c | 37 ++++++++++++++++++-----------
> drivers/gpu/drm/xe/xe_gt_ccs_mode.h | 12 ++++++++++
> 2 files changed, 35 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_gt_ccs_mode.c b/drivers/gpu/drm/xe/xe_gt_ccs_mode.c
> index e146e00b0ca2..52285a550f34 100644
> --- a/drivers/gpu/drm/xe/xe_gt_ccs_mode.c
> +++ b/drivers/gpu/drm/xe/xe_gt_ccs_mode.c
> @@ -13,6 +13,7 @@
> #include "xe_gt_sysfs.h"
> #include "xe_mmio.h"
> #include "xe_sriov.h"
> +#include "xe_sriov_pf.h"
>
> static void __xe_gt_apply_ccs_mode(struct xe_gt *gt, u32 num_engines)
> {
> @@ -117,12 +118,6 @@ ccs_mode_store(struct device *kdev, struct device_attribute *attr,
> u32 num_engines, num_slices;
> int ret;
>
> - if (IS_SRIOV(xe)) {
> - xe_gt_dbg(gt, "Can't change compute mode when running as %s\n",
> - xe_sriov_mode_to_string(xe_device_sriov_mode(xe)));
> - return -EOPNOTSUPP;
> - }
> -
> ret = kstrtou32(buff, 0, &num_engines);
> if (ret)
> return ret;
> @@ -139,21 +134,35 @@ ccs_mode_store(struct device *kdev, struct device_attribute *attr,
> }
>
> /* CCS mode can only be updated when there are no drm clients */
> - mutex_lock(&xe->drm.filelist_mutex);
> + guard(mutex)(&xe->drm.filelist_mutex);
> if (!list_empty(&xe->drm.filelist)) {
> - mutex_unlock(&xe->drm.filelist_mutex);
> xe_gt_dbg(gt, "Rejecting compute mode change as there are active drm clients\n");
> return -EBUSY;
> }
>
> - if (gt->ccs_mode != num_engines) {
> - xe_gt_info(gt, "Setting compute mode to %d\n", num_engines);
> - gt->ccs_mode = num_engines;
> - xe_gt_record_user_engines(gt);
> - xe_gt_reset(gt);
> + if (gt->ccs_mode == num_engines)
> + return count;
> +
> + /*
> + * Changing default CCS mode is only allowed when there
> + * are no VFs. Try to lockdown PF to find out.
> + */
> + if (xe_gt_ccs_mode_default(gt) && IS_SRIOV_PF(xe)) {
> + ret = xe_sriov_pf_lockdown(xe);
> + if (ret) {
> + xe_gt_dbg(gt, "Can't change CCS Mode: VFs are enabled\n");
> + return ret;
> + }
> }
>
> - mutex_unlock(&xe->drm.filelist_mutex);
> + xe_gt_info(gt, "Setting compute mode to %d\n", num_engines);
> + gt->ccs_mode = num_engines;
> + xe_gt_record_user_engines(gt);
> + xe_gt_reset(gt);
> +
> + /* We may end PF lockdown once CCS mode is default again */
> + if (xe_gt_ccs_mode_default(gt) && IS_SRIOV_PF(xe))
> + xe_sriov_pf_end_lockdown(xe);
>
> return count;
> }
> diff --git a/drivers/gpu/drm/xe/xe_gt_ccs_mode.h b/drivers/gpu/drm/xe/xe_gt_ccs_mode.h
> index f8779852cf0d..53a595b0882c 100644
> --- a/drivers/gpu/drm/xe/xe_gt_ccs_mode.h
> +++ b/drivers/gpu/drm/xe/xe_gt_ccs_mode.h
> @@ -20,5 +20,17 @@ static inline bool xe_gt_ccs_mode_enabled(const struct xe_gt *gt)
> return hweight32(CCS_MASK(gt)) > 1;
> }
>
> +/**
> + * xe_gt_ccs_mode_default() - Check if CCS mode is default (single CCS mode)
> + * @gt: GT structure
> + *
> + * Return: %true if actual CCS mode is single mode, or
> + * %false otherwise (CCS in alternate/multi mode)
> + */
> +static inline bool xe_gt_ccs_mode_default(struct xe_gt *gt)
> +{
> + return gt->ccs_mode == 1;
> +}
nit: do we need this as public helper ?
maybe it should be defined as simple static function in .c ?
> +
> #endif
>
but the code change LGTM, so with commit msg improved,
Reviewed-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
next prev parent reply other threads:[~2026-01-29 21:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 17:18 [PATCH v1 0/2] drm/xe:Mutual exclusivity between CCS-mode and PF Nareshkumar Gollakoti
2025-11-28 17:18 ` [PATCH v1 1/2] drm/xe: Fix Prevent VFs from exposing the CCS mode sysfs file Nareshkumar Gollakoti
2025-11-28 17:18 ` [PATCH v1 2/2] drm/xe: Mutual exclusivity between CCS-mode and PF Nareshkumar Gollakoti
2025-12-03 8:52 ` K V P, Satyanarayana
2025-12-03 12:13 ` Michal Wajdeczko
2025-12-03 12:43 ` Kumar G, Naresh
2025-11-28 17:31 ` ✓ CI.KUnit: success for drm/xe:Mutual " Patchwork
2025-11-28 18:46 ` ✓ Xe.CI.BAT: " Patchwork
2025-11-28 19:54 ` ✗ Xe.CI.Full: failure " Patchwork
2025-12-15 5:49 ` Kumar G, Naresh
2026-01-29 17:22 ` [PATCH v2 0/2] " Nareshkumar Gollakoti
2026-01-29 17:22 ` [PATCH v2 1/2] drm/xe: Fix Prevent VFs from exposing the CCS mode sysfs file Nareshkumar Gollakoti
2026-01-29 21:13 ` Michal Wajdeczko
2026-01-30 14:32 ` Kumar G, Naresh
2026-01-30 15:16 ` Rodrigo Vivi
2026-02-06 14:37 ` Kumar G, Naresh
2026-01-29 17:22 ` [PATCH v2 2/2] drm/xe: Mutual exclusivity between CCS-mode and PF Nareshkumar Gollakoti
2026-01-29 21:41 ` Michal Wajdeczko [this message]
2026-01-30 14:33 ` Kumar G, Naresh
-- strict thread matches above, loose matches on Subject: below --
2026-01-30 9:44 [PATCH v2 0/2] drm/xe:Mutual " Nareshkumar Gollakoti
2026-01-30 9:44 ` [PATCH v2 2/2] drm/xe: Mutual " Nareshkumar Gollakoti
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=8bf19afa-44ab-458b-9cb7-178cfb8d0373@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=naresh.kumar.g@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