From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Yunxiang Li <Yunxiang.Li@amd.com>,
dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
christian.koenig@amd.com, tvrtko.ursulin@igalia.com
Cc: Alexander.Deucher@amd.com
Subject: Re: [PATCH v6 4/5] drm: add drm_memory_stats_is_zero
Date: Thu, 31 Oct 2024 13:34:13 +0100 [thread overview]
Message-ID: <5b1153e7-9304-41fb-83d7-0ca0bfb4123e@gmail.com> (raw)
In-Reply-To: <20241025174113.554-5-Yunxiang.Li@amd.com>
Am 25.10.24 um 19:41 schrieb Yunxiang Li:
> Add a helper to check if the memory stats is zero, this will be used to
> check for memory accounting errors.
>
> Signed-off-by: Yunxiang Li <Yunxiang.Li@amd.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
In theory I would need to upstream that through the drm-misc-next
channel, but I think that's simply enough that we can take it through
amd-staging-drm-next.
Regards,
Christian.
> ---
> drivers/gpu/drm/drm_file.c | 9 +++++++++
> include/drm/drm_file.h | 1 +
> 2 files changed, 10 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_file.c b/drivers/gpu/drm/drm_file.c
> index 714e42b051080..75ed701d80f74 100644
> --- a/drivers/gpu/drm/drm_file.c
> +++ b/drivers/gpu/drm/drm_file.c
> @@ -859,6 +859,15 @@ static void print_size(struct drm_printer *p, const char *stat,
> drm_printf(p, "drm-%s-%s:\t%llu%s\n", stat, region, sz, units[u]);
> }
>
> +int drm_memory_stats_is_zero(const struct drm_memory_stats *stats) {
> + return (stats->shared == 0 &&
> + stats->private == 0 &&
> + stats->resident == 0 &&
> + stats->purgeable == 0 &&
> + stats->active == 0);
> +}
> +EXPORT_SYMBOL(drm_memory_stats_is_zero);
> +
> /**
> * drm_print_memory_stats - A helper to print memory stats
> * @p: The printer to print output to
> diff --git a/include/drm/drm_file.h b/include/drm/drm_file.h
> index ab230d3af138d..7f91e35d027d9 100644
> --- a/include/drm/drm_file.h
> +++ b/include/drm/drm_file.h
> @@ -477,6 +477,7 @@ struct drm_memory_stats {
>
> enum drm_gem_object_status;
>
> +int drm_memory_stats_is_zero(const struct drm_memory_stats *stats);
> void drm_print_memory_stats(struct drm_printer *p,
> const struct drm_memory_stats *stats,
> enum drm_gem_object_status supported_status,
next prev parent reply other threads:[~2024-10-31 12:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 17:41 [PATCH v6 0/5] rework bo mem stats tracking Yunxiang Li
2024-10-25 17:41 ` [PATCH v6 1/5] drm/amdgpu: remove unused function parameter Yunxiang Li
2024-10-25 17:41 ` [PATCH v6 2/5] drm/amdgpu: make drm-memory-* report resident memory Yunxiang Li
2024-10-25 17:41 ` [PATCH v6 3/5] drm/amdgpu: stop tracking visible memory stats Yunxiang Li
2024-10-25 17:41 ` [PATCH v6 4/5] drm: add drm_memory_stats_is_zero Yunxiang Li
2024-10-31 12:34 ` Christian König [this message]
2024-11-07 10:41 ` Tvrtko Ursulin
2024-11-07 14:17 ` Li, Yunxiang (Teddy)
2024-11-07 14:43 ` Tvrtko Ursulin
2024-11-07 14:47 ` Christian König
2024-10-25 17:41 ` [PATCH v6 5/5] drm/amdgpu: track bo memory stats at runtime Yunxiang Li
2024-10-31 12:53 ` Christian König
2024-10-31 13:48 ` Li, Yunxiang (Teddy)
2024-11-07 10:48 ` Tvrtko Ursulin
2024-11-07 14:24 ` Li, Yunxiang (Teddy)
2024-11-07 14:55 ` 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=5b1153e7-9304-41fb-83d7-0ca0bfb4123e@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=Alexander.Deucher@amd.com \
--cc=Yunxiang.Li@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=tvrtko.ursulin@igalia.com \
/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