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 B8D69C5321D for ; Wed, 21 Aug 2024 15:28:42 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 7547310E32C; Wed, 21 Aug 2024 15:28:42 +0000 (UTC) Authentication-Results: gabe.freedesktop.org; dkim=pass (2048-bit key; unprotected) header.d=intel.com header.i=@intel.com header.b="Sh8EGjEv"; dkim-atps=neutral Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.20]) by gabe.freedesktop.org (Postfix) with ESMTPS id 48B9810E327 for ; Wed, 21 Aug 2024 15:28:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1724254113; x=1755790113; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=xjSMF4DH+/bnBU/jKwVrrHlLR0dn07HLmRxlZ0ciovo=; b=Sh8EGjEv9zkPfLPb0Eq+Nm1mGrlixG7IaNmAjqhAMPgudmU9ACMk7OaI z4bO/eLCrxgKeaZ2ebrJnQF9JpnmeqwTNNz1RRggncOYg5V7QcpD38juV subUhzn9J7gJ37iAPIVacAKrLixOT9PBT0QwXji8ZzGeecjj8f7BdOAVC vFlp/OYJiy4DvM/stSO9g1DfXV8RWXH5WQodLpruVO3ldXYI5NcsT+Brt 8JzfqAuLLt+DvhbuhB7cX34oWQUN7rlVBkEIjzfiA8AHxpT2JS2mgODRx OvPIDoBg5jURKxCz+0ETeJ36xSgd065HK6w7BwefSTBaFEyEFQmO+BgDp Q==; X-CSE-ConnectionGUID: ZLHNFzE3SaO9Img0MahRmA== X-CSE-MsgGUID: yj0YgeWdQNW7emMykUJ1sQ== X-IronPort-AV: E=McAfee;i="6700,10204,11171"; a="22427396" X-IronPort-AV: E=Sophos;i="6.10,164,1719903600"; d="scan'208";a="22427396" Received: from orviesa008.jf.intel.com ([10.64.159.148]) by orvoesa112.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Aug 2024 08:28:32 -0700 X-CSE-ConnectionGUID: axy1es0yTn2P8/+RK7HHOA== X-CSE-MsgGUID: /zH8l/obTBO3YnVV8IYKFQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.10,164,1719903600"; d="scan'208";a="61877109" Received: from orsosgc001.jf.intel.com ([10.165.21.138]) by orviesa008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Aug 2024 08:28:34 -0700 From: Ashutosh Dixit To: intel-xe@lists.freedesktop.org Cc: Matthew Brost , Jose Souza , Lionel Landwerlin , Umesh Nerlige Ramappa , Jonathan Cavitt Subject: [PATCH v3 0/7] drm/xe/oa: xe_syncs for OA Date: Wed, 21 Aug 2024 08:28:23 -0700 Message-ID: <20240821152830.1495276-1-ashutosh.dixit@intel.com> X-Mailer: git-send-email 2.41.0 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" OA stream configuration submits batches which can be queued behind other (say workload) batches. Also, in some cases, additional delay is needed for an OA configuration to take effect, even after programming batches have completed executing on HW. Mesa has use cases where a single workload is replayed repeatedly on the GPU, each time with a different OA configuration (or metric set), in order to capture different aspects of workload performance. This requires that OA configuration takes effect at precisely the correct input batch and also userspace is correctly informed when a new configuration has been activated (at batch granularity). In the previous implementation this is implemented by introducing a delay in the stream open and reconfiguration ioctl's. This works, except that we introdce a bubble in the userspace pipeline (the pipeline stalls during the delays in calls into these ioctl's). Mesa prefers that such pipeline stalls don't happen. In this series this problem is solved using xe_sync arrays, similar to xe_exec and vm_bind. Here OA re-configuration can be made to wait till input fences signal and OA will signal output fences after a new configuration has been activated. This can of course be done without stalling the userspace pipeline. v2: Address review comments from Matt Brost, Jonathan Cavitt and Jose Souza v3: Changes to Patch 4 and Patch 7 to address review comments from Matt Brost and Jonathan Cavitt Test-with: 20240820003104.1407398-1-ashutosh.dixit@intel.com Ashutosh Dixit (7): drm/xe/oa: Separate batch submission from waiting for completion drm/xe/oa/uapi: Define and parse OA sync properties drm/xe/oa: Add input fence dependencies drm/xe/oa: Signal output fences drm/xe/oa: Move functions up so they can be reused for config ioctl drm/xe/oa: Add syncs support to OA config ioctl drm/xe/oa: Allow only certain property changes from config drivers/gpu/drm/xe/xe_oa.c | 642 +++++++++++++++++++++---------- drivers/gpu/drm/xe/xe_oa_types.h | 12 + drivers/gpu/drm/xe/xe_query.c | 2 +- include/uapi/drm/xe_drm.h | 17 + 4 files changed, 470 insertions(+), 203 deletions(-) -- 2.41.0