Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 95B04606A331 for ; Thu, 19 Nov 2026 14:17:00 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.a=rsa-sha256 header.s=Intel header.b=b/wjZpXc Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 14F2B10E115; Thu, 19 Nov 2026 14:16:55 +0000 (UTC) Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.12]) by gabe.freedesktop.org (Postfix) with ESMTPS id B9A0010ED41 for ; Thu, 19 Nov 2026 14:16:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1795097808; x=1826633808; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=XnSRKwhJlgq+2q+6GYNi2ukTZvSpE5J2dgKeqYPGzYI=; b=b/wjZpXcO4ysm0llGqJp01j9mrDKemtMaoPiDUVTtbuyNusTPCspQQAz tVDOaljKTdF3+ZuFFB5XLrxQZIRyncNvBm5PL4BNO5MMsLXDQPKSOBSk2 D4Azvtz52AQ3Wd99c4XtkSeTxWglBJ+23KyovEm8MJlr/0LVtQiSmEHfb t/Ucin+VyLGGIky3t/oBfs7yWibPnikqxe78hqBkHB6jpLOEBydqE6iqT N8uvVdMplTXItlz1NRCm4hNQHJf7f9ff8z+zCfKxpCXDs4Z0XywNg+Zvz srAaMG9RqTyElUyiqZS6ogsGxCFqId9DNqERmUZ+KzD2oiq9+Cns1H5n2 Q==; X-CSE-ConnectionGUID: sKg4iobeRX+cNKISN5KQcA== X-CSE-MsgGUID: QExTC3bdTgee2jAj5trQNw== X-IronPort-AV: E=McAfee;i="6800,10657,11971"; a="3829218" X-IronPort-AV: E=Sophos;i="6.27,221,1787036400"; d="scan'208";a="3829218" Received: from orviesa004.jf.intel.com ([10.64.159.144]) by orvoesa104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 19 Nov 2026 06:16:48 -0800 X-CSE-ConnectionGUID: Bn4azHzcRPGkAht2RXkd0A== X-CSE-MsgGUID: Ga0NYNalRLqpESpGpcFOhA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.27,221,1787036400"; d="scan'208";a="10309539" Received: from gkczarna.igk.intel.com ([10.211.131.163]) by orviesa004.jf.intel.com with ESMTP; 19 Nov 2026 06:16:47 -0800 From: Tomasz Lis To: intel-xe@lists.freedesktop.org Cc: Matthew Brost , =?UTF-8?q?Micha=C5=82=20Winiarski?= , =?UTF-8?q?Piotr=20Pi=C3=B3rkowski?= , Satyanarayana K V P Subject: [PATCH v5 0/2] drm/xe/vf: New approach for post-migration LRC fixups Date: Thu, 19 Nov 2026 15:17:39 +0100 Message-ID: <20261119141741.1720650-1-tomasz.lis@intel.com> X-Mailer: git-send-email 2.43.0 X-Archived-By: 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-Archive: List-Post: List-Help: List-Subscribe: , Sender: "Intel-xe" X-Spam-Status: No, score=-18.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_CR_TRAILER,INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_GIT autolearn=ham autolearn_force=no version=4.0.1 X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-26) on aws-us-west-2-korg-listserv-alma10-1 The current approach to LRC recovery requires caution from developers when modifying any LRC-related code. More flexible solution may allow to avoid future troubles. The current code also includes LRC creation repeat which looks a bit suspicious - it was developed without detailed knowledge of which part of LRC creation requires a repeat. Now after extensive debug we know that the repeat is only required for BO mapping, and actually all BOs should be protected, not only the ones storing LRCs. This fixes a very rare bug where BO would be incorrectly created during migration resulting in CAT error generated by GPU. Chances of triggering this error were well below 0.1%. v2: A rebase after 6 months, with adjustments to current source. v3: Re-adding a check carelessly removed in v2, fixed handling GGTT start/end, fixed issue with signals. v4: Several fixes to error paths (mutex creation, and prolonged migration recovery while BO mapping). Altered BO insertion to not repeat placement in GGTT upon migration, only repeat the mapping. v5: Disallow signals affecting BO insertion. Add cleanup of of BO mapping on recovery fail. Signed-off-by: Tomasz Lis Tomasz Lis (2): drm/xe/vf: Late fixups of LRCs after VF migration drm/xe: After VF migration, repeat BO mapping in progress drivers/gpu/drm/xe/xe_exec_queue.c | 63 +++++++++++++---------- drivers/gpu/drm/xe/xe_exec_queue.h | 2 +- drivers/gpu/drm/xe/xe_ggtt.c | 57 +++++++++++++++++--- drivers/gpu/drm/xe/xe_gt_sriov_vf.c | 23 +++++---- drivers/gpu/drm/xe/xe_gt_sriov_vf_types.h | 2 + drivers/gpu/drm/xe/xe_guc_submit.c | 35 +++---------- drivers/gpu/drm/xe/xe_guc_submit.h | 2 - drivers/gpu/drm/xe/xe_memirq.c | 10 +++- 8 files changed, 114 insertions(+), 80 deletions(-) -- 2.43.0