From: Steven Price <steven.price@arm.com>
To: "Adrián Larumbe" <adrian.larumbe@collabora.com>,
"Boris Brezillon" <boris.brezillon@collabora.com>,
"Liviu Dudau" <liviu.dudau@arm.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>
Cc: kernel@collabora.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/2] drm/panthor: Expose size of driver internal BO's over fdinfo
Date: Fri, 20 Dec 2024 11:12:28 +0000 [thread overview]
Message-ID: <42ec58fd-d570-43a0-b440-cd0983e6d1e9@arm.com> (raw)
In-Reply-To: <awusmheh5i3qnhgyubf2gxmam6oio7xleb2wbnnsylhbhzfqtt@b4q66zp7i2ci>
On 18/12/2024 19:14, Adrián Larumbe wrote:
> On 19.12.2024 02:18, Adrián Martínez Larumbe wrote:
>> From: Adrián Larumbe <adrian.larumbe@collabora.com>
>>
>> This will display the sizes of kenrel BO's bound to an open file, which are
>> otherwise not exposed to UM through a handle.
>>
>> The sizes recorded are as follows:
>> - Per group: suspend buffer, protm-suspend buffer, syncobjcs
>> - Per queue: ringbuffer, profiling slots, firmware interface
>> - For all heaps in all heap pools across all VM's bound to an open file,
>> record size of all heap chuks, and for each pool the gpu_context BO too.
>>
>> This does not record the size of FW regions, as these aren't bound to a
>> specific open file and remain active through the whole life of the driver.
>>
>> Signed-off-by: Adrián Larumbe <adrian.larumbe@collabora.com>
>> Reviewed-by: Liviu Dudau <liviu.dudau@arm.com>
>> ---
[...]
>> +size_t panthor_heap_pool_size(struct panthor_heap_pool *pool)
>> +{
>> + struct panthor_heap *heap;
>> + unsigned long i;
>> + size_t size = 0;
>> +
>> + down_read(&pool->lock);
>> + xa_for_each(&pool->xa, i, heap)
>> + size += heap->chunk_size * heap->chunk_count;
>> + up_write(&pool->lock);
>
> Oh well, just realised I forgot to change this to up_read() so will do in a final revision.
With that fixed, feel free to add:
Reviewed-by: Steven Price <steven.price@arm.com>
Thanks,
Steve
next prev parent reply other threads:[~2024-12-20 11:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 18:18 [PATCH v5 0/2] drm/panthor: Display size of internal kernel BOs through fdinfo Adrián Martínez Larumbe
2024-12-18 18:18 ` [PATCH v5 1/2] drm/panthor: Expose size of driver internal BO's over fdinfo Adrián Martínez Larumbe
2024-12-18 19:14 ` Adrián Larumbe
2024-12-20 11:12 ` Steven Price [this message]
2024-12-19 16:30 ` Mihail Atanassov
2024-12-20 11:08 ` Steven Price
2024-12-20 11:14 ` Mihail Atanassov
2025-01-02 20:35 ` Adrián Martínez Larumbe
2024-12-20 21:06 ` kernel test robot
2024-12-18 18:18 ` [PATCH v5 2/2] Documentation/gpu: Add fdinfo meanings of drm-*-internal memory tags Adrián Martínez Larumbe
2024-12-19 13:06 ` Liviu Dudau
2024-12-20 11:13 ` Steven Price
2025-01-02 21:59 ` Tvrtko Ursulin
2025-01-02 22:18 ` Adrián Martínez Larumbe
2025-01-03 10:49 ` Tvrtko Ursulin
2025-01-06 16:53 ` Adrián Martínez Larumbe
2025-01-07 10:43 ` Tvrtko Ursulin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42ec58fd-d570-43a0-b440-cd0983e6d1e9@arm.com \
--to=steven.price@arm.com \
--cc=adrian.larumbe@collabora.com \
--cc=airlied@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®