From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: "Adrián Larumbe" <adrian.larumbe@collabora.com>,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, daniel@ffwll.ch,
robdclark@gmail.com, quic_abhinavk@quicinc.com,
dmitry.baryshkov@linaro.org, sean@poorly.run,
marijn.suijten@somainline.org, robh@kernel.org,
steven.price@arm.com
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, freedreno@lists.freedesktop.org,
healych@amazon.com, kernel@collabora.com,
tvrtko.ursulin@linux.intel.com, boris.brezillon@collabora.com
Subject: Re: [PATCH v7 2/5] drm/panfrost: Add fdinfo support GPU load metrics
Date: Thu, 28 Sep 2023 13:24:55 +0200 [thread overview]
Message-ID: <3fd7e291-4254-c6b3-893a-b8e457cccb58@collabora.com> (raw)
In-Reply-To: <20230927213133.1651169-3-adrian.larumbe@collabora.com>
Il 27/09/23 23:29, Adrián Larumbe ha scritto:
> The drm-stats fdinfo tags made available to user space are drm-engine,
> drm-cycles, drm-max-freq and drm-curfreq, one per job slot.
>
> This deviates from standard practice in other DRM drivers, where a single
> set of key:value pairs is provided for the whole render engine. However,
> Panfrost has separate queues for fragment and vertex/tiler jobs, so a
> decision was made to calculate bus cycles and workload times separately.
>
> Maximum operating frequency is calculated at devfreq initialisation time.
> Current frequency is made available to user space because nvtop uses it
> when performing engine usage calculations.
>
> It is important to bear in mind that both GPU cycle and kernel time numbers
> provided are at best rough estimations, and always reported in excess from
> the actual figure because of two reasons:
> - Excess time because of the delay between the end of a job processing,
> the subsequent job IRQ and the actual time of the sample.
> - Time spent in the engine queue waiting for the GPU to pick up the next
> job.
>
> To avoid race conditions during enablement/disabling, a reference counting
> mechanism was introduced, and a job flag that tells us whether a given job
> increased the refcount. This is necessary, because user space can toggle
> cycle counting through a debugfs file, and a given job might have been in
> flight by the time cycle counting was disabled.
>
> The main goal of the debugfs cycle counter knob is letting tools like nvtop
> or IGT's gputop switch it at any time, to avoid power waste in case no
> engine usage measuring is necessary.
>
> Add also documentation file explaining the possible values for fdinfo's
Also add a documentation file explaining .....
or
Moreover, add a documentation file explaining .....
> engine keystrings and Panfrost-specific drm-curfreq-<keystr> pairs.
>
> Signed-off-by: Adrián Larumbe <adrian.larumbe@collabora.com>
> Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>
> Reviewed-by: Steven Price <steven.price@arm.com>
Nitpick apart:
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
next prev parent reply other threads:[~2023-09-28 11:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 21:29 [PATCH v7 0/5] Add fdinfo support to Panfrost Adrián Larumbe
2023-09-27 21:29 ` [PATCH v7 1/5] drm/panfrost: Add cycle count GPU register definitions Adrián Larumbe
2023-09-28 11:24 ` AngeloGioacchino Del Regno
2023-09-27 21:29 ` [PATCH v7 2/5] drm/panfrost: Add fdinfo support GPU load metrics Adrián Larumbe
2023-09-28 11:24 ` AngeloGioacchino Del Regno [this message]
2023-09-27 21:29 ` [PATCH v7 3/5] drm/panfrost: Add fdinfo support for memory stats Adrián Larumbe
2023-09-28 11:24 ` AngeloGioacchino Del Regno
2023-09-27 21:29 ` [PATCH v7 4/5] drm/drm_file: Add DRM obj's RSS reporting function for fdinfo Adrián Larumbe
2023-09-28 11:24 ` AngeloGioacchino Del Regno
2023-09-27 21:29 ` [PATCH v7 5/5] drm/panfrost: Implement generic DRM object RSS reporting function Adrián Larumbe
2023-09-28 11:24 ` AngeloGioacchino Del Regno
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=3fd7e291-4254-c6b3-893a-b8e457cccb58@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=adrian.larumbe@collabora.com \
--cc=airlied@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=daniel@ffwll.ch \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=healych@amazon.com \
--cc=kernel@collabora.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marijn.suijten@somainline.org \
--cc=mripard@kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=robh@kernel.org \
--cc=sean@poorly.run \
--cc=steven.price@arm.com \
--cc=tvrtko.ursulin@linux.intel.com \
--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