From: Tvrtko Ursulin <tursulin@ursulin.net>
To: "Adrián Larumbe" <adrian.larumbe@collabora.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>,
"Jonathan Corbet" <corbet@lwn.net>
Cc: kernel@collabora.com, dri-devel@lists.freedesktop.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 1/4] Documentation/gpu: Clarify format of driver-specific fidnfo keys
Date: Thu, 9 Jan 2025 12:56:03 +0000 [thread overview]
Message-ID: <8d856a0e-9226-405d-857a-35c2807e35fe@ursulin.net> (raw)
In-Reply-To: <20250108210259.647030-2-adrian.larumbe@collabora.com>
On 08/01/2025 21:02, Adrián Larumbe wrote:
> This change reflects de facto usage by amdgpu, as exemplified by commit
> d6530c33a978 ("drm/amdgpu: expose more memory stats in fdinfo").
>
> Signed-off-by: Adrián Larumbe <adrian.larumbe@collabora.com>
> Cc: Tvrtko Ursulin <tursulin@ursulin.net>
> ---
> Documentation/gpu/drm-usage-stats.rst | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/gpu/drm-usage-stats.rst b/Documentation/gpu/drm-usage-stats.rst
> index 2717cb2a597e..2b5393ed7692 100644
> --- a/Documentation/gpu/drm-usage-stats.rst
> +++ b/Documentation/gpu/drm-usage-stats.rst
> @@ -21,7 +21,10 @@ File format specification
>
> - File shall contain one key value pair per one line of text.
> - Colon character (`:`) must be used to delimit keys and values.
> -- All keys shall be prefixed with `drm-`.
> +- All standardised keys shall be prefixed with `drm-`.
> +- Driver-specific keys shall be prefixed with `driver_name-`, where
> + driver_name should ideally be the same as the `name` field in
> + `struct drm_driver`, although this is not mandatory.
> - Whitespace between the delimiter and first non-whitespace character shall be
> ignored when parsing.
> - Keys are not allowed to contain whitespace characters.
LGTM, thanks for documenting it!
Acked-by: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
Native english speaker maybe could clarify if s/Driver-specific/Driver
specific/ would be more correct.
Regards,
Tvrtko
next prev parent reply other threads:[~2025-01-09 12:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 21:02 [PATCH v7 0/4] drm/panthor: Display size of internal kernel BOs through fdinfo Adrián Larumbe
2025-01-08 21:02 ` [PATCH v7 1/4] Documentation/gpu: Clarify format of driver-specific fidnfo keys Adrián Larumbe
2025-01-09 12:56 ` Tvrtko Ursulin [this message]
2025-01-08 21:02 ` [PATCH v7 2/4] drm/file: Add driver-specific memory region key printing helper Adrián Larumbe
2025-01-09 13:05 ` Tvrtko Ursulin
2025-01-09 17:17 ` Adrián Larumbe
2025-01-08 21:02 ` [PATCH v7 3/4] drm/panthor: Expose size of driver internal BO's over fdinfo Adrián Larumbe
2025-01-08 21:02 ` [PATCH v7 4/4] Documentation/gpu: Add fdinfo meanings of drm-*-internal memory tags Adrián Larumbe
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=8d856a0e-9226-405d-857a-35c2807e35fe@ursulin.net \
--to=tursulin@ursulin.net \
--cc=adrian.larumbe@collabora.com \
--cc=airlied@gmail.com \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@collabora.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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®