From nobody Fri Nov 29 18:47:08 2024 Received: from mail-ej1-f47.google.com (mail-ej1-f47.google.com [209.85.218.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 904E516A94B; Tue, 17 Sep 2024 11:14:35 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.218.47 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1726571677; cv=none; b=F/684cyTnuEcGyj4/fLc3OmWPuZfaCwHbPBYGYJgZmvzMWL1iwpXRe40gFwC2KIDLgOxNsJAlNzeF/C9g30yx2t/S3JXGVZXr1WW1k6G/T5qf9GjI9zbCxarei+axc73V5BOl4PDLaoqlpIlMsQbymsi2oPFiCEW6xzjc7BCfQo= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1726571677; c=relaxed/simple; bh=roRdoUA06OSktfkT3cuEuaM2HtScD0650/8+GaZZFy4=; h=From:Date:Subject:MIME-Version:Content-Type:Message-Id:References: In-Reply-To:To:Cc; b=LhEDFztIOeN2eDc/h9C6OTEr7vB4prlNzRLTQLpVwdGyufZooktS34X3xbvDIuG+ia/kU1E9qCu4HGnLCAQ8AZX8VaB3ritj2POFgDsqtjVpHwpFRE55knwD4vQkutv4olKRIuHExqseXTDUVJYNTtF890jf0x+f+vq+zR9EKMc= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b=ZCKsMQ2C; arc=none smtp.client-ip=209.85.218.47 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="ZCKsMQ2C" Received: by mail-ej1-f47.google.com with SMTP id a640c23a62f3a-a8a7cdfdd80so647439466b.0; Tue, 17 Sep 2024 04:14:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1726571674; x=1727176474; darn=vger.kernel.org; h=cc:to:in-reply-to:references:message-id:content-transfer-encoding :mime-version:subject:date:from:from:to:cc:subject:date:message-id :reply-to; bh=Bo/Q+fVB0c2N2S+2tO3u0tNQvOs02ddpFS55PdIBqiM=; b=ZCKsMQ2C2QkijTjt1FKdat4VS9xLVJXFsvwGrgSCbUiI5SZh/Y+eyBDqfMHZcGcOdb kMV8lgI+DhyVAN59/31GY4VtD8nY1jHsnPLv38uO68INuSZ79m0aW9Ay6Jwv9L/fC278 h0VXgQnvJKivKtDGp/q4kDqWWcka55tkmc7wiupxV4cQlyrmJ8ECMnO6hhwiwlX/tJ7c S4DmsmxW31mERlp5hDn1v5HdXQ9e0yHGWowsYzVR1lfthi3iTVYQ1HLl9ZvNLnHE93Sp LUMARLlgiev1nZS99JcGZQ0Wqp5vOkkericjtNXtMYXMhWTmGd3GC1AuU5GPKkSEKwWG bcWw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726571674; x=1727176474; h=cc:to:in-reply-to:references:message-id:content-transfer-encoding :mime-version:subject:date:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Bo/Q+fVB0c2N2S+2tO3u0tNQvOs02ddpFS55PdIBqiM=; b=tMbvf2lZ8w3LVm7IN5FiT4BG5wUzGEy0LC0F+VXmAOUu0/Cpj/MisoJbeG4wXyOZIU IXAUScpfG+XqTVj17FOwrGSQwKldyUGSxXAKx9hL/9bCt/rGnSnWWFcEAoS4GdUp39nU jtVReS1FFOowfYZ6Rqn9FLJWuI41836d22rUm3O3gaotEV+7cQG+WcCbuAB5gNT7cEeV 1o2rzEB51FevdIYYyhLeexOqGxPMA3GiMgnHlDfdDBQ1JvTIRwCBHIJ0QEiN7us7hzAg UYCLpVeulhwQawa3Ia5hYAQIGbcN237lHw8VFYOcEaODxOZOgrHgSuhIi3XbYkuf4wI1 J+GA== X-Forwarded-Encrypted: i=1; AJvYcCWRWEovW8fYO7KdVcAWev5SykuZb3n3AlVKV2EgsPUX/EZO+D58g6dmYJvX2/mFP+khS/TPQkUVmfmZoJnU@vger.kernel.org, AJvYcCWXiBICZqHaP9tU/xEmMbIf4r7lxDFzHq2vvUh4+pIKeql3hCtrHjo5vyz8XivtGQgVysCECYclZPo=@vger.kernel.org X-Gm-Message-State: AOJu0YwPAZ0TgjglQ/52r9xXT6aXz1E9JYVfDMTIA9Z/9XPRN5wdA5DD pxhBBEsal29m9atMJ9pahn41loUtMK2r4nDchgnf8+B1T9qW3TiK X-Google-Smtp-Source: AGHT+IEo3KeisOhfYxWfOemIFnRDGajHBF3QYONL7b0c6BlfR/CJVVBqL7wK41v8Afv13g1KcnHV7A== X-Received: by 2002:a17:907:7f23:b0:a86:700f:93c0 with SMTP id a640c23a62f3a-a9047d1ac6dmr1292392066b.35.1726571673826; Tue, 17 Sep 2024 04:14:33 -0700 (PDT) Received: from [192.168.1.17] (host-82-51-105-30.retail.telecomitalia.it. [82.51.105.30]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-a90612e1a55sm430745166b.157.2024.09.17.04.14.31 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 17 Sep 2024 04:14:33 -0700 (PDT) From: Antonino Maniscalco Date: Tue, 17 Sep 2024 13:14:21 +0200 Subject: [PATCH v4 11/11] Documentation: document adreno preemption Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <20240917-preemption-a750-t-v4-11-95d48012e0ac@gmail.com> References: <20240917-preemption-a750-t-v4-0-95d48012e0ac@gmail.com> In-Reply-To: <20240917-preemption-a750-t-v4-0-95d48012e0ac@gmail.com> To: Rob Clark , Sean Paul , Konrad Dybcio , Abhinav Kumar , Dmitry Baryshkov , Marijn Suijten , David Airlie , Daniel Vetter , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , Jonathan Corbet Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, Antonino Maniscalco X-Mailer: b4 0.14.1 X-Developer-Signature: v=1; a=ed25519-sha256; t=1726571652; l=4842; i=antomani103@gmail.com; s=20240815; h=from:subject:message-id; bh=roRdoUA06OSktfkT3cuEuaM2HtScD0650/8+GaZZFy4=; b=DNGawWdMty8okiDt/7j6ItVwD17WNPGrPDbSn6xIln3BXwF6VZLrsXi+qTJkgXjZ0nc1r6J1j nOxyBYuU/5SB91rFRyxpLOw6+WqT369DmPmh3TVRpAnUPU2sdutlD24 X-Developer-Key: i=antomani103@gmail.com; a=ed25519; pk=0zicFb38tVla+iHRo4kWpOMsmtUrpGBEa7LkFF81lyY= Add documentation about the preemption feature supported by the msm driver. Signed-off-by: Antonino Maniscalco --- Documentation/gpu/msm-preemption.rst | 98 ++++++++++++++++++++++++++++++++= ++++ 1 file changed, 98 insertions(+) diff --git a/Documentation/gpu/msm-preemption.rst b/Documentation/gpu/msm-p= reemption.rst new file mode 100644 index 000000000000..c1203524da2e --- /dev/null +++ b/Documentation/gpu/msm-preemption.rst @@ -0,0 +1,98 @@ +.. SPDX-License-Identifier: GPL-2.0 + +:orphan: + +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D +MSM Preemtion +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D + +Preemption allows Adreno GPUs to switch to an higher priority ring when wo= rk is +pushed to it, reducing latency for high priority submissions. + +When preemption is enabled 4 rings are initialized, corresponding to diffe= rent +priority levels. Having multiple rings is purely a software concept as the= GPU +only has registers to keep track of one graphics ring. +The kernel is able to switch which ring is currently being processed by +requesting preemption. When certain conditions are met, depending on the +priority level, the GPU will save its current state in a series of buffers, +then restores state from a similar set of buffers specified by the kernel.= It +then resumes execution and fires an IRQ to let the kernel know the context +switch has completed. + +This mechanism can be used by the kernel to switch between rings. Whenever= a +submission occurs the kernel finds the highest priority ring which isn't e= mpty +and preempts to it if said ring is not the one being currently executed. T= his is +also done whenever a submission completes to make sure execution resumes o= n a +lower priority ring when a higher priority ring is done. + +Preemption levels +----------------- + +Preemption can only occur at certain boundaries. The exact conditions can = be +configured by changing the preemption level, this allows to compromise bet= ween +latency (ie. the time that passes between when the kernel requests preempt= ion +and when the SQE begins saving state) and overhead (the amount of state th= at +needs to be saved). + +The GPU offers 3 levels: + +Level 0 + Preemption only occurs at the submission level. This requires the least = amount + of state to be saved as the execution of userspace submitted IBs is never + interrupted, however it offers very little benefit compared to not enabl= ing + preemption of any kind. + +Level 1 + Preemption occurs at either bin level, if using GMEM rendering, or draw = level + in the sysmem rendering case. + +Level 2 + Preemption occurs at draw level. + +Level 1 is the mode that is used by the msm driver. + +Additionally the GPU allows to specify a `skip_save_restore` option. This +disables the saving and restoring of certain registers which lowers the +overhead. When enabling this userspace is expected to set the state that i= sn't +preserved whenever preemption occurs which is done by specifying preamble = and +postambles. Those are IBs that are executed before and after +preemption. + +Preemption buffers +------------------ + +A series of buffers are necessary to store the state of rings while they a= re not +being executed. There are different kinds of preemption records and most of +those require one buffer per ring. This is because preemption never occurs +between submissions on the same ring, which always run in sequence when th= e ring +is active. This means that only one context per ring is effectively active. + +SMMU_INFO + This buffer contains info about the current SMMU configuration such as t= he + ttbr0 register. The SQE firmware isn't actually able to save this record. + As a result SMMU info must be saved manually from the CP to a buffer and= the + SMMU record updated with info from said buffer before triggering + preemption. + +NON_SECURE + This is the main preemption record where most state is saved. It is most= ly + opaque to the kernel except for the first few words that must be initial= ized + by the kernel. + +SECURE + This saves state related to the GPU's secure mode. + +NON_PRIV + The intended purpose of this record is unknown. The SQE firmware actually + ignores it and therefore msm doesn't handle it. + +COUNTER + This record is used to save and restore performance counters. + +Handling the permissions of those buffers is critical for security. All bu= t the +NON_PRIV records need to be inaccessible from userspace, so they must be m= apped +in the kernel address space with the MSM_BO_MAP_PRIV flag. +For example, making the NON_SECURE record accessible from userspace would = allow +any process to manipulate a saved ring's RPTR which can be used to skip the +execution of some packets in a ring and execute user commands with higher +privileges. --=20 2.46.0