From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Nareshkumar Gollakoti <naresh.kumar.g@intel.com>,
<intel-xe@lists.freedesktop.org>,
Matthew Brost <matthew.brost@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH v2 1/2] drm/xe: Fix Prevent VFs from exposing the CCS mode sysfs file
Date: Thu, 29 Jan 2026 22:13:16 +0100 [thread overview]
Message-ID: <fc0f819c-0712-4b27-8cb2-38462cfc7381@intel.com> (raw)
In-Reply-To: <20260129172246.1106097-5-naresh.kumar.g@intel.com>
On 1/29/2026 6:22 PM, Nareshkumar Gollakoti wrote:
> Skipping creation of sysfs file in VF Mode to ensure VFs do not expose
> CCS mode changes
>
> Fixes: f3bc5bb4d53d2 ("drm/xe: Allow userspace to configure CCS mode")
shouldn't this be
Fixes: 97fedf015cd9 ("drm/xe: Use fixed CCS mode when running in SR-IOV mode")
or since it wasn't really broken, maybe we need no Fixes tag at all?
adding maintainers to confirm
> Signed-off-by: Nareshkumar Gollakoti <naresh.kumar.g@intel.com>
> ---
> drivers/gpu/drm/xe/xe_gt_ccs_mode.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_gt_ccs_mode.c b/drivers/gpu/drm/xe/xe_gt_ccs_mode.c
> index 50fffc9ebf62..e146e00b0ca2 100644
> --- a/drivers/gpu/drm/xe/xe_gt_ccs_mode.c
> +++ b/drivers/gpu/drm/xe/xe_gt_ccs_mode.c
> @@ -191,7 +191,7 @@ int xe_gt_ccs_mode_sysfs_init(struct xe_gt *gt)
> struct xe_device *xe = gt_to_xe(gt);
> int err;
>
> - if (!xe_gt_ccs_mode_enabled(gt))
> + if (!xe_gt_ccs_mode_enabled(gt) || IS_SRIOV_VF(xe))
> return 0;
I guess there should be no users on VFs that would like to read it back
(as CCS mode was/is always fixed/const for VFs), so this fine,
Reviewed-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
>
> err = sysfs_create_files(gt->sysfs, gt_ccs_mode_attrs);
next prev parent reply other threads:[~2026-01-29 21:13 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 [this message]
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
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 1/2] drm/xe: Fix Prevent VFs from exposing the CCS mode sysfs file 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=fc0f819c-0712-4b27-8cb2-38462cfc7381@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
--cc=naresh.kumar.g@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