From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Matthew Auld <matthew.auld@intel.com>,
intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915/debugfs: hook up ttm_resource_manager_debug
Date: Thu, 26 Aug 2021 11:51:44 +0200 [thread overview]
Message-ID: <4d14b5f5f74d279d666077de28f5de7f6d721509.camel@linux.intel.com> (raw)
In-Reply-To: <YSdcAD7Pa+e93xqh@phenom.ffwll.local>
On Thu, 2021-08-26 at 11:16 +0200, Daniel Vetter wrote:
> On Thu, Aug 19, 2021 at 09:32:20AM +0200, Thomas Hellström wrote:
> > 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?
>
> Imo we should just emebed ttm_resource_mager into our own and not try
> to
> abstract this all away that much. At least in upstream there is just
> not
> going to be another memory region implementation, and for backporting
> I'm
> not sure these abstractions really help that much - we're touching
> all the
> same code still in the end.
Hmm, yes. Here I was seeing the separation between the debugfs code and
the intel_memory_region code, rather between the latter and TTM.
The i915 driver is currently much "everything uses everything" which
IMHO is not really good for code understanding and maintainance.
/Thomas
> -Daniel
next prev parent reply other threads:[~2021-08-26 9:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 14:58 [PATCH 1/2] drm/i915/buddy: add some pretty printing Matthew Auld
2021-08-18 14:58 ` [PATCH 2/2] drm/i915/debugfs: hook up ttm_resource_manager_debug Matthew Auld
2021-08-19 7:32 ` Thomas Hellström
2021-08-26 9:16 ` Daniel Vetter
2021-08-26 9:51 ` Thomas Hellström [this message]
2021-08-26 10:00 ` Thomas Hellström
2021-08-26 10:03 ` Daniel Vetter
2021-08-26 10:36 ` Daniel Vetter
2021-08-19 7:15 ` [PATCH 1/2] drm/i915/buddy: add some pretty printing 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=4d14b5f5f74d279d666077de28f5de7f6d721509.camel@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=daniel@ffwll.ch \
--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