All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Paulo Zanoni <paulo.r.zanoni@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/3] drm/i915: Make the report about a bogus stolen reserved area an error
Date: Tue, 14 Nov 2017 22:41:07 +0200	[thread overview]
Message-ID: <20171114204107.GR10981@intel.com> (raw)
In-Reply-To: <1510691621.22559.14.camel@intel.com>

On Tue, Nov 14, 2017 at 06:33:41PM -0200, Paulo Zanoni wrote:
> Em Qui, 2017-11-02 às 17:17 +0200, Ville Syrjala escreveu:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > 
> > Now that we should be properly filtering out the cases when the
> > stolen
> > reserved area is disabled, let's convert the debug message about a
> > misplaced reserved area into an error.
> 
> Worst that could happen is that some unhappy user will notify us that
> we may still be missing something.
> 
> Speaking of that, is CI already able to call our attention to boot
> error messages like this one?

I guess module reload should hit it. Would be nice to have checks for
initial boot errors/warnings too though since there's no guarantee
everything is 100% virgin on module reload.

> 
> Reviewed-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
> 
> > 
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> >  drivers/gpu/drm/i915/i915_gem_stolen.c | 6 +++---
> >  1 file changed, 3 insertions(+), 3 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/i915_gem_stolen.c
> > b/drivers/gpu/drm/i915/i915_gem_stolen.c
> > index 44a5dbc8c23b..4f9377b5f4ae 100644
> > --- a/drivers/gpu/drm/i915/i915_gem_stolen.c
> > +++ b/drivers/gpu/drm/i915/i915_gem_stolen.c
> > @@ -503,9 +503,9 @@ int i915_gem_init_stolen(struct drm_i915_private
> > *dev_priv)
> >  	if (reserved_base < dev_priv->mm.stolen_base ||
> >  	    reserved_base + reserved_size > stolen_top) {
> >  		dma_addr_t reserved_top = reserved_base +
> > reserved_size;
> > -		DRM_DEBUG_KMS("Stolen reserved area [%pad - %pad]
> > outside stolen memory [%pad - %pad]\n",
> > -			      &reserved_base, &reserved_top,
> > -			      &dev_priv->mm.stolen_base,
> > &stolen_top);
> > +		DRM_ERROR("Stolen reserved area [%pad - %pad]
> > outside stolen memory [%pad - %pad]\n",
> > +			  &reserved_base, &reserved_top,
> > +			  &dev_priv->mm.stolen_base, &stolen_top);
> >  		return 0;
> >  	}
> >  

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-11-14 20:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-02 15:17 [PATCH 1/3] drm/i915: Check if the stolen memory "reserved" area is enabled or not Ville Syrjala
2017-11-02 15:17 ` [PATCH 2/3] drm/i915: Make the report about a bogus stolen reserved area an error Ville Syrjala
2017-11-14 20:33   ` Paulo Zanoni
2017-11-14 20:41     ` Ville Syrjälä [this message]
2017-11-02 15:17 ` [PATCH 3/3] drm/i915: Use ELK stolen memory reserved detection for ILK Ville Syrjala
2017-11-14 20:59   ` Paulo Zanoni
2017-11-14 21:19     ` Ville Syrjälä
2017-11-02 15:38 ` ✓ Fi.CI.BAT: success for series starting with [1/3] drm/i915: Check if the stolen memory "reserved" area is enabled or not Patchwork
2017-11-02 16:34 ` ✗ Fi.CI.IGT: warning " Patchwork
2017-11-02 17:08   ` Ville Syrjälä
2017-11-03  7:19     ` Saarinen, Jani
2017-11-03  8:18     ` Tomi Sarvela
2017-11-03 10:41       ` Ville Syrjälä
2017-11-03 11:14         ` Tomi Sarvela
2017-11-03 10:43       ` Petri Latvala
2017-11-03 11:33         ` Tomi Sarvela
2017-11-03 12:53           ` Tomi Sarvela
2017-11-03 12:52 ` ✓ Fi.CI.IGT: success " Patchwork
2017-11-14 20:12 ` [PATCH 1/3] " Paulo Zanoni
2017-11-14 20:19   ` Chris Wilson
2017-11-14 20:29     ` Paulo Zanoni
2017-11-14 20:41       ` Chris Wilson
2017-11-14 20:34   ` Ville Syrjälä
2017-11-14 20:44     ` Paulo Zanoni
2017-11-14 21:38       ` Ville Syrjälä
2017-11-15 17:11 ` Ville Syrjälä

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=20171114204107.GR10981@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=paulo.r.zanoni@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.