Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Daniel Vetter <daniel@ffwll.ch>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Only print the info message about incresing stolen size for FBC once
Date: Fri, 26 Apr 2013 17:43:51 +0200	[thread overview]
Message-ID: <20130426154351.GQ6169@phenom.ffwll.local> (raw)
In-Reply-To: <20130426150606.GC12865@cantiga.alporthouse.com>

On Fri, Apr 26, 2013 at 04:06:06PM +0100, Chris Wilson wrote:
> On Fri, Apr 26, 2013 at 04:46:12PM +0200, Daniel Vetter wrote:
> > On Fri, Apr 26, 2013 at 02:04:25PM +0100, Chris Wilson wrote:
> > > Instead of repeatedly bombarding the user with a request to reboot and
> > > increase the stolen size with every fb refresh, just inform them the
> > > first time only.
> > > 
> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > ---
> > >  drivers/gpu/drm/i915/intel_pm.c |    3 +--
> > >  1 file changed, 1 insertion(+), 2 deletions(-)
> > > 
> > > diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
> > > index 3534a71..05bc0a4 100644
> > > --- a/drivers/gpu/drm/i915/intel_pm.c
> > > +++ b/drivers/gpu/drm/i915/intel_pm.c
> > > @@ -481,8 +481,7 @@ void intel_update_fbc(struct drm_device *dev)
> > >  		goto out_disable;
> > >  
> > >  	if (i915_gem_stolen_setup_compression(dev, intel_fb->obj->base.size)) {
> > > -		DRM_INFO("not enough stolen space for compressed buffer (need %zd bytes), disabling\n", intel_fb->obj->base.size);
> > > -		DRM_INFO("hint: you may be able to increase stolen memory size in the BIOS to avoid this\n");
> > > +		pr_info_once("not enough stolen space for compressed buffer (need %zd bytes), disabling. Hint: you may be able to inrease stolen memory size in hte BIOS to avoid this.\n", intel_fb->obj->base.size);
> > s/hte/the/ in the above line while at it?
> 
> The other problem is that we drop the "drm: ", so perhaps we should add
> that back in (or start using "drm/i915: " or "i915: ").

I've looked through all the macros, and there doesn't seem to be a
dev_info_once version. While we discuss debug output, I still wonder
whether we should eventually switch over to the dynamic device debug
stuff. But I'm not sure whether that's really better than the current
scheme.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2013-04-26 15:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-26 13:04 [PATCH] drm/i915: Only print the info message about incresing stolen size for FBC once Chris Wilson
2013-04-26 14:46 ` Daniel Vetter
2013-04-26 15:06   ` Chris Wilson
2013-04-26 15:43     ` Daniel Vetter [this message]
2013-04-27 11:44   ` Chris Wilson
2013-04-27 11:51     ` Daniel Vetter

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=20130426154351.GQ6169@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=chris@chris-wilson.co.uk \
    --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