From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>, intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 2/2] drm/i915/debugfs: hook up ttm_resource_manager_debug
Date: Thu, 19 Aug 2021 09:32:20 +0200 [thread overview]
Message-ID: <811cc4bfb6262d9050140ed9a9eac1dd7632d33a.camel@linux.intel.com> (raw)
In-Reply-To: <20210818145850.225387-2-matthew.auld@intel.com>
On Wed, 2021-08-18 at 15:58 +0100, Matthew Auld wrote:
> This should give a more complete view of the various bits of internal
> resource manager state, for device local-memory.
>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> ---
> drivers/gpu/drm/i915/i915_debugfs.c | 12 +++++++++---
> 1 file changed, 9 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_debugfs.c
> b/drivers/gpu/drm/i915/i915_debugfs.c
> index eec0d349ea6a..109e6feed6be 100644
> --- a/drivers/gpu/drm/i915/i915_debugfs.c
> +++ b/drivers/gpu/drm/i915/i915_debugfs.c
> @@ -238,6 +238,7 @@ i915_debugfs_describe_obj(struct seq_file *m,
> struct drm_i915_gem_object *obj)
> static int i915_gem_object_info(struct seq_file *m, void *data)
> {
> struct drm_i915_private *i915 = node_to_i915(m->private);
> + struct drm_printer p = drm_seq_file_printer(m);
> struct intel_memory_region *mr;
> enum intel_region_id id;
>
> @@ -245,9 +246,14 @@ static int i915_gem_object_info(struct seq_file
> *m, void *data)
> i915->mm.shrink_count,
> atomic_read(&i915->mm.free_count),
> i915->mm.shrink_memory);
> - for_each_memory_region(mr, i915, id)
> - seq_printf(m, "%s: total:%pa, available:%pa bytes\n",
> - mr->name, &mr->total, &mr->avail);
> + for_each_memory_region(mr, i915, id) {
> + seq_printf(m, "%s: ", mr->name);
> + if (mr->region_private)
> + ttm_resource_manager_debug(mr-
> >region_private, &p);
> + else
> + seq_printf(m, "total:%pa, available:%pa
> bytes\n",
> + &mr->total, &mr->avail);
Hm. Shouldn't we make the above intel_memory_region_debug() or perhaps
intel_memory_region_info() to avoid using memory region internals
directly here?
/Thomas
next prev parent reply other threads:[~2021-08-19 7:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 14:58 [Intel-gfx] [PATCH 1/2] drm/i915/buddy: add some pretty printing Matthew Auld
2021-08-18 14:58 ` [Intel-gfx] [PATCH 2/2] drm/i915/debugfs: hook up ttm_resource_manager_debug Matthew Auld
2021-08-19 7:32 ` Thomas Hellström [this message]
2021-08-26 9:16 ` Daniel Vetter
2021-08-26 9:51 ` Thomas Hellström
2021-08-26 10:00 ` Thomas Hellström
2021-08-26 10:03 ` Daniel Vetter
2021-08-26 10:36 ` Daniel Vetter
2021-08-18 18:00 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915/buddy: add some pretty printing Patchwork
2021-08-19 7:15 ` [Intel-gfx] [PATCH 1/2] " Thomas Hellström
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=811cc4bfb6262d9050140ed9a9eac1dd7632d33a.camel@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.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