From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 3A08DD116EA for ; Fri, 28 Nov 2025 17:17:01 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id D22C010E18B; Fri, 28 Nov 2025 17:17:00 +0000 (UTC) Authentication-Results: gabe.freedesktop.org; dkim=pass (2048-bit key; unprotected) header.d=intel.com header.i=@intel.com header.b="bWeXccfv"; dkim-atps=neutral Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.9]) by gabe.freedesktop.org (Postfix) with ESMTPS id 1947110E18B for ; Fri, 28 Nov 2025 17:16:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1764350219; x=1795886219; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=q+sYjO3V+mGgPXvfI2YMNGo7lhwGH+of1oaG84gxd80=; b=bWeXccfv3IfxGrckcY2vWtMLoQYN87iYSzcNa4B7LPI2BP9x8D2v2FlK RuTYbqx4OyQ7dciS6iWl0HYZwG2glsiTgVPdGUT7jUXmLT1j4DqN7Er5q b/3LrBiQMdaylzTDhaIFxR+D1oPwVNXKlCy+Mjy+ioGYTqosj58SF60A+ vThiw0jNe8Xptmlp27uMcCf1MdeKZACkPU4VdFYsH2ySmgAB1gBknpdsA jDmnV0s4ALf7xlGrHWWd1zxc0dsCvgyAGoEwIMOXT93RtrHLO4zUyUYNT 3rFpm2//Z+R9D8cDzM4Yk7/XDLxbSSKDBXiK5xMPC31NRtTTA1nFhM2KR w==; X-CSE-ConnectionGUID: fM3DQYEWQcKRdNQFQNpTng== X-CSE-MsgGUID: a0+JNTsBSC+/BpYCJxkJgw== X-IronPort-AV: E=McAfee;i="6800,10657,11626"; a="77071445" X-IronPort-AV: E=Sophos;i="6.20,234,1758610800"; d="scan'208";a="77071445" Received: from fmviesa002.fm.intel.com ([10.60.135.142]) by fmvoesa103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Nov 2025 09:16:59 -0800 X-CSE-ConnectionGUID: LwrZFvY3StiqtP4cROVoCA== X-CSE-MsgGUID: VL8MmkL9RJCD/lAGwl8/fg== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.20,234,1758610800"; d="scan'208";a="216853594" Received: from naresh-nuc8i7beh.iind.intel.com (HELO nkumarg-desk.iind.intel.com) ([10.190.216.171]) by fmviesa002.fm.intel.com with ESMTP; 28 Nov 2025 09:16:57 -0800 From: Nareshkumar Gollakoti To: intel-xe@lists.freedesktop.org Cc: michal.wajdeczko@intel.com, Nareshkumar Gollakoti Subject: [PATCH v1 0/2] Mutual exclusivity between CCS-mode and PF Date: Fri, 28 Nov 2025 22:40:31 +0530 Message-ID: <20251128171030.2774942-4-naresh.kumar.g@intel.com> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20251128123843.2763356-2-naresh.kumar.g@intel.com> References: <20251128123843.2763356-2-naresh.kumar.g@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: intel-xe@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Intel Xe graphics driver List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-xe-bounces@lists.freedesktop.org Sender: "Intel-xe" Due to SLA agreement between PF and VFs,the alternate CCS-mode cannot be changed when VFs are already enabled. Similarly, enabling VFs is not permitted when the alternate CCS-mode is active. Also skipping populating CCS-mode sysfs entry in VF Mode. --- v2: - function xe_device_is_vf_enabled has been refactored to xe_sriov_pf_has_vfs_enabled and moved to xe_sriov_pf_helper.h. - The code now distinctly checks for SR-IOV VF mode and SR-IOV PF with VFs enabled. - Log messages have been updated to explicitly state the current mode. - The function xe_multi_ccs_mode_enabled is moved to xe_device.h v3: Described missed arg documentation for xe_sriov_pf_has_vfs_enabled v4: - sysfs interface for CCS mode is not initialized when operating in SRIOV VF Mode. - xe_sriov_pf_has_vfs_enabled() check is sufficient while CCS mode enablement. - remove unnecessary comments as flow is self explanatory. v5:(review comments from Michal) - Add xe device level CCS mode block with mutex lock and CCS mode state - necessesary functions to manage ccs mode state to provide strict mutual exclusive support b/w CCS mode & SRIOV VF enabling v6: - Re modeled implementation based on lockdown the PF using custom guard supported functions by Michal v7: - Corrected patch style as message written as subject - Used public PF lockdown functions instead internal funcions(Michal) - Creating CCS Mode entries only on PF Mode v8:(Michal) - updated short subject and few comments - used guard for mutex - Add a check of PF Mode to ensure use of xe_sriov_pf_lockdown only in PF Mode - Added default CCS mode check to xe_gt_ccs_mode_default(gt) function v9:(Michal) - Added xe_gt_ccs_mode_default(gt) as static inline and it can be used across driver to use between default or alternate CCS mode - removed comment from obvious code 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 | 61 ++++++++++++++++++++++------- drivers/gpu/drm/xe/xe_gt_ccs_mode.h | 12 ++++++ 2 files changed, 58 insertions(+), 15 deletions(-) -- 2.43.0