From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 93FDD1C07CD for ; Fri, 20 Dec 2024 11:13:36 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=217.140.110.172 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1734693218; cv=none; b=Py/dMfJyx9i+DEfWSJTfHShAK4g4hgk31eOihNBM3RD+4onwJz2TPbz0G+1Z2yzj+fwCsXhyXkN9Xv2Y3DgEepNXuTyF8BXixewhRiMwrhyuKwI9ZN3GTDzdGb7v7Jj6eNtkPbV9RWUDk+ZRSonASWB3XZhUeb1B6XcsQhSky+E= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1734693218; c=relaxed/simple; bh=K86g8zWdSMBOEl1Lszzz7LuDWHk8v2H5Id2ZnRtn+U4=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=NqqWoiXNAt2tUU0invGcecL0fxHw7JNpxTAFMEikBbMhGwyR0As4hVTmu+aAvCuPY9eqYkvVVhfg+OxPUOZMmuaC/ZX2eWdV7gu4lk9AdKZj0Ch24oHDYbE6Vs/tpmg1XwPKb/7DSPWIO5SPNYf9cfiAgNQ8Sej8+TII+TBRNTc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com; spf=pass smtp.mailfrom=arm.com; arc=none smtp.client-ip=217.140.110.172 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=arm.com Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 2AD381480; Fri, 20 Dec 2024 03:14:04 -0800 (PST) Received: from [10.1.31.19] (e122027.cambridge.arm.com [10.1.31.19]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id CFB4F3F58B; Fri, 20 Dec 2024 03:13:33 -0800 (PST) Message-ID: <486e5467-d7fd-41a2-bd80-85afb53d141f@arm.com> Date: Fri, 20 Dec 2024 11:13:31 +0000 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v5 2/2] Documentation/gpu: Add fdinfo meanings of drm-*-internal memory tags To: =?UTF-8?Q?Adri=C3=A1n_Mart=C3=ADnez_Larumbe?= , Boris Brezillon , Liviu Dudau , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , David Airlie , Simona Vetter Cc: kernel@collabora.com, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Mihail Atanassov References: <20241218181844.886043-1-adrian.larumbe@collabora.com> <20241218181844.886043-3-adrian.larumbe@collabora.com> From: Steven Price Content-Language: en-GB In-Reply-To: <20241218181844.886043-3-adrian.larumbe@collabora.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit On 18/12/2024 18:18, Adrián Martínez Larumbe wrote: > From: Adrián Larumbe > > A previous commit enabled display of driver-internal kernel BO sizes > through the device file's fdinfo interface. > > Expand the description of the relevant driver-specific key:value pairs > with the definitions of the new drm-*-internal ones. > > Signed-off-by: Adrián Larumbe > Reviewed-by: Mihail Atanassov Reviewed-by: Steven Price > --- > Documentation/gpu/panthor.rst | 14 ++++++++++++++ > 1 file changed, 14 insertions(+) > > diff --git a/Documentation/gpu/panthor.rst b/Documentation/gpu/panthor.rst > index 3f8979fa2b86..23aa3d67c9d2 100644 > --- a/Documentation/gpu/panthor.rst > +++ b/Documentation/gpu/panthor.rst > @@ -26,6 +26,10 @@ the currently possible format options: > drm-cycles-panthor: 94439687187 > drm-maxfreq-panthor: 1000000000 Hz > drm-curfreq-panthor: 1000000000 Hz > + drm-total-internal: 10396 KiB > + drm-shared-internal: 0 > + drm-active-internal: 10396 KiB > + drm-resident-internal: 10396 KiB > drm-total-memory: 16480 KiB > drm-shared-memory: 0 > drm-active-memory: 16200 KiB > @@ -44,3 +48,13 @@ driver by writing into the appropriate sysfs node:: > > Where `N` is a bit mask where cycle and timestamp sampling are respectively > enabled by the first and second bits. > + > +Possible `drm-*-internal` keys are: `total`, `active`, `resident` and `shared`. > +These values convey the sizes of the internal driver-owned shmem BO's that > +aren't exposed to user-space through a DRM handle, like queue ring buffers, > +sync object arrays and heap chunks. Because they are all allocated and pinned > +at creation time, `drm-resident-internal` and `drm-total-internal` should always > +be equal. `drm-active-internal` shows the size of kernel BO's associated with > +VM's and groups currently being scheduled for execution by the GPU. > +`drm-shared-internal` is unused at present, but in the future it might stand for > +the size of executable FW regions, since they do not belong to an open file context.