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 3F94BC3601A for ; Wed, 2 Apr 2025 15:29:08 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 0031910E80B; Wed, 2 Apr 2025 15:29:07 +0000 (UTC) Authentication-Results: gabe.freedesktop.org; dkim=pass (2048-bit key; unprotected) header.d=intel.com header.i=@intel.com header.b="NrpPPCN1"; dkim-atps=neutral Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.9]) by gabe.freedesktop.org (Postfix) with ESMTPS id 0A92C10E7B5 for ; Wed, 2 Apr 2025 15:29:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1743607747; x=1775143747; h=from:to:subject:date:message-id:mime-version: content-transfer-encoding; bh=h670G5guZjbU+REx/9u6xzqCkSRc1bI7KKCjwzGoMUk=; b=NrpPPCN1LzD0PW+Y/K9doskos0KC2a+zbEN8BJT9+x3r72jasmdg9Fl6 ggD2+2IjO117mhA6i80lEjrZ6AThnaAyUA6SEs4Q3C/yK0buR7EvQtb9B yrBnIAQ/LQclHVZJJ4QWNhc++J+Z/q0gkgPLylQbLSfi609cxnRhskWEj XuVT0nZ0mpE/x03AgKDwOle4BArS+SMZ1Eox2Es5kx+Eh6GToUj7ARgIT n6RWXVD2grWqNZT8473qIULoGgYInELE9oAZ1JNlYz/1AekX4tN3uBWrP iYUH9OAl9gYBZGSiU055YrmLBg1EfwvmSoHzWP017jzOd75KBe3AvQRpP w==; X-CSE-ConnectionGUID: vHlzNdmGSzO3ZfffaaQ96g== X-CSE-MsgGUID: esjFNnVxSdWUytZOXMTPIw== X-IronPort-AV: E=McAfee;i="6700,10204,11392"; a="67447224" X-IronPort-AV: E=Sophos;i="6.15,182,1739865600"; d="scan'208";a="67447224" Received: from orviesa001.jf.intel.com ([10.64.159.141]) by orvoesa101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Apr 2025 08:29:06 -0700 X-CSE-ConnectionGUID: yAIBtpgwTdKacd7uRpweAg== X-CSE-MsgGUID: Q/xSlqQuSWKB67fqafP10w== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.15,182,1739865600"; d="scan'208";a="163969963" Received: from szeng-desk.jf.intel.com ([10.165.21.160]) by smtpauth.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Apr 2025 08:29:06 -0700 From: Oak Zeng To: intel-xe@lists.freedesktop.org Subject: [PATCH v9 0/3] Allow scratch page under fault mode for certain platform Date: Wed, 2 Apr 2025 11:45:59 -0400 Message-Id: <20250402154602.2431681-1-oak.zeng@intel.com> X-Mailer: git-send-email 2.26.3 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 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" Normally scratch page is not allowed when a vm is operate under page fault mode, i.e., in the existing codes, DRM_XE_VM_CREATE_FLAG_SCRATCH_PAGE and DRM_XE_VM_CREATE_FLAG_FAULT_MODE are mutual exclusive. The reason is fault mode relies on recoverable page to work, while scratch page can mute recoverable page fault. On xe2 and xe3, out of bound prefetch can cause page fault and further system hang because xekmd can't resolve such page fault. SYCL and OCL language runtime requires out of bound prefetch to be silently dropped without causing any functional problem, thus the existing behavior doesn't meet language runtime requirement. At the same time, HW prefetching can cause page fault interrupt. Due to page fault interrupt overhead (i.e., need Guc and KMD involved to fix the page fault), HW prefetching can be slowed by many orders of magnitude. Fix those problems by allowing scratch page under fault mode for xe2 and xe3. With scratch page in place, HW prefetching could always hit scratch page instead of causing interrupt. A side effect is, scratch page could hide application program error. Application out of bound accesses are hided by scratch page mapping, instead of get reported to user. igt test: https://patchwork.freedesktop.org/series/144907/, Test result on BMG: root@DUT1130BMGFRD:/home/szeng/dii-tools/igt-public/build/tests# ./xe_exec_fault_mode --run-subtest scratch-fault IGT-Version: 1.30-gde1a3cb42 (x86_64) (Linux: 6.13.0-xe x86_64) Using IGT_SRANDOM=1738684805 for randomisation Opened device: /dev/dri/card0 Starting subtest: scratch-fault Subtest scratch-fault: SUCCESS (0.080s) Oak Zeng (3): drm/xe: Introduced needs_scratch bit in device descriptor drm/xe: Clear scratch page on vm_bind drm/xe: Allow scratch page under fault mode for certain platform drivers/gpu/drm/xe/xe_device_types.h | 2 + drivers/gpu/drm/xe/xe_pci.c | 5 ++ drivers/gpu/drm/xe/xe_pt.c | 97 +++++++++++++++++----------- drivers/gpu/drm/xe/xe_vm.c | 31 +++++++-- drivers/gpu/drm/xe/xe_vm_types.h | 2 + include/uapi/drm/xe_drm.h | 6 +- 6 files changed, 100 insertions(+), 43 deletions(-) -- 2.26.3