From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Andrzej Hajda <andrzej.hajda@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 02/12] drm/i915: Print memory region info during probe
Date: Wed, 13 Dec 2023 18:26:13 +0200 [thread overview]
Message-ID: <ZXnbJYwjA6xrldnX@intel.com> (raw)
In-Reply-To: <fc2dbf45-cd58-460a-99c5-fc8934331e0e@intel.com>
On Wed, Dec 13, 2023 at 05:05:21PM +0100, Andrzej Hajda wrote:
> On 13.12.2023 01:42, Ville Syrjala wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Dump the details about every memory region into dmesg at probe time.
> > Avoids having to dig those out from random places when debugging stuff.
> >
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_memory_region.c | 18 ++++++++++++++++++
> > 1 file changed, 18 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_memory_region.c b/drivers/gpu/drm/i915/intel_memory_region.c
> > index b2708f8cac2a..52d998e5c21a 100644
> > --- a/drivers/gpu/drm/i915/intel_memory_region.c
> > +++ b/drivers/gpu/drm/i915/intel_memory_region.c
> > @@ -372,6 +372,24 @@ int intel_memory_regions_hw_probe(struct drm_i915_private *i915)
> > i915->mm.regions[i] = mem;
> > }
> >
> > + for (i = 0; i < ARRAY_SIZE(i915->mm.regions); i++) {
> > + struct intel_memory_region *mem = i915->mm.regions[i];
> > + u64 region_size, io_size;
> > +
> > + if (!mem)
> > + continue;
> > +
> > + region_size = resource_size(&mem->region) >> 20;
> > + io_size = resource_size(&mem->io) >> 20;
> > +
> > + if (resource_size(&mem->io))
> > + drm_dbg(&i915->drm, "Memory region(%d): %s: %llu MiB %pR, io: %llu MiB %pR\n",
> > + mem->id, mem->name, region_size, &mem->region, io_size, &mem->io);
> > + else
> > + drm_dbg(&i915->drm, "Memory region(%d): %s: %llu MiB %pR, io: n/a\n",
> > + mem->id, mem->name, region_size, &mem->region);
>
> Doesn't printk handle properly 0-length resources?
Not without extra help. Apparently there is IORESOURCE_UNSET
that would just print the size, but you have to explicitly
set that yourself, which I suppose we could do.
>
> Reviewed-by: Andrzej Hajda <andrzej.hajda@intel.com>
>
> Regards
> Andrzej
>
>
> > + }
> > +
> > return 0;
> >
> > out_cleanup:
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2023-12-13 16:26 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 0:42 [PATCH 00/12] drm/i915: (stolen) memory region related fixes Ville Syrjala
2023-12-13 0:42 ` [PATCH 01/12] drm/i915: Use struct resource for memory region IO as well Ville Syrjala
2023-12-13 0:59 ` Ville Syrjälä
2023-12-13 17:01 ` Ville Syrjälä
2023-12-13 15:52 ` Andrzej Hajda
2023-12-13 16:08 ` Ville Syrjälä
2023-12-13 0:42 ` [PATCH 02/12] drm/i915: Print memory region info during probe Ville Syrjala
2023-12-13 16:05 ` Andrzej Hajda
2023-12-13 16:26 ` Ville Syrjälä [this message]
2023-12-13 16:49 ` Ville Syrjälä
2023-12-13 0:42 ` [PATCH 03/12] drm/i915: Remove ad-hoc lmem/stolen debugs Ville Syrjala
2023-12-13 16:06 ` Andrzej Hajda
2023-12-13 0:42 ` [PATCH 04/12] drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access Ville Syrjala
2023-12-13 9:09 ` Joonas Lahtinen
2023-12-13 9:30 ` Ville Syrjälä
2023-12-13 20:18 ` Sripada, Radhakrishna
2023-12-14 2:03 ` Ville Syrjälä
2023-12-14 21:06 ` Sripada, Radhakrishna
2023-12-15 10:23 ` Ville Syrjälä
2023-12-13 0:42 ` [PATCH 05/12] drm/i915: Disable the "binder" Ville Syrjala
2023-12-13 0:42 ` [PATCH 06/12] drm/i915: Rename the DSM/GSM registers Ville Syrjala
2023-12-13 0:42 ` [PATCH 07/12] drm/i915: Fix PTE decode during initial plane readout Ville Syrjala
2023-12-13 0:42 ` [PATCH 08/12] drm/i915: Fix region start " Ville Syrjala
2023-12-13 0:42 ` [PATCH 09/12] drm/i915: Fix MTL " Ville Syrjala
2023-12-13 0:42 ` [PATCH 10/12] drm/i915: s/phys_base/dma_addr/ Ville Syrjala
2023-12-13 0:42 ` [PATCH 11/12] drm/i915: Split the smem and lmem plane readout apart Ville Syrjala
2023-12-13 0:42 ` [PATCH 12/12] drm/i915: Simplify intel_initial_plane_config() calling convention Ville Syrjala
2023-12-13 1:22 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: (stolen) memory region related fixes Patchwork
2023-12-13 1:22 ` ✗ Fi.CI.SPARSE: " Patchwork
2023-12-13 1:37 ` ✗ Fi.CI.BAT: failure " Patchwork
2023-12-13 16:13 ` â " Andrzej Hajda
2023-12-13 17:24 ` Tvrtko Ursulin
2023-12-13 17:28 ` Tvrtko Ursulin
2023-12-14 11:06 ` â " Andrzej Hajda
2023-12-14 23:01 ` Ville Syrjälä
2023-12-15 8:23 ` Ville Syrjälä
2023-12-13 4:31 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: (stolen) memory region related fixes (rev2) Patchwork
2023-12-13 4:31 ` ✗ Fi.CI.SPARSE: " Patchwork
2023-12-13 4:49 ` ✗ Fi.CI.BAT: failure " Patchwork
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=ZXnbJYwjA6xrldnX@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=andrzej.hajda@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/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;
as well as URLs for NNTP newsgroup(s).