public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	Ben Widawsky <ben@bwidawsk.net>,
	Alessandro Suardi <alessandro.suardi@gmail.com>
Subject: Re: [PATCH] drm/i915: Sanitize the enable_ppgtt module option once
Date: Wed, 23 Apr 2014 09:18:03 +0200	[thread overview]
Message-ID: <20140423071803.GU10722@phenom.ffwll.local> (raw)
In-Reply-To: <20140422212215.GB22645@nuc-i3427.alporthouse.com>

On Tue, Apr 22, 2014 at 10:22:15PM +0100, Chris Wilson wrote:
> On Tue, Apr 22, 2014 at 10:17:50PM +0200, Daniel Vetter wrote:
> > Otherwise we'll end up spamming dmesg on every context creation on snb
> > with vt-d enabled. This regression was introduced in
> > 
> > commit 246cbfb5fb9a1ca0997fbb135464c1ff5bb9c549
> > Author: Ben Widawsky <benjamin.widawsky@intel.com>
> > Date:   Fri Dec 6 14:11:14 2013 -0800
> > 
> >     drm/i915: Reorganize intel_enable_ppgtt
> 
> I started to consider what would happen if i915.enable_ppgtt changed on
> the fly, but then saw that it is 0400 and this pre-initialisation makes
> a lot of sense. So maybe we could mention that here:
> 
> As the i915.enable_ppgtt is read-only it cannot be changed after the
> module is loaded and so we can perform an early sanitization of the
> values.
> 
> > References: https://lkml.org/lkml/2014/4/17/599
> > Cc: Alessandro Suardi <alessandro.suardi@gmail.com>
> > Cc: Ben Widawsky <ben@bwidawsk.net>
> > Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> 
> If you care to add in some of the comments,
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>

Fully agreed on both since the first thing I've checked is that the
enable_ppgtt option is indeed 0400 ;-)

Jani, can you please apply Chris' commit message text and comment when
merging?
-Daniel

> 
> >  drivers/gpu/drm/i915/i915_gem_gtt.c | 26 +++++++++++++++++++-------
> >  1 file changed, 19 insertions(+), 7 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/i915_gem_gtt.c b/drivers/gpu/drm/i915/i915_gem_gtt.c
> > index 0d514ff9b94c..47491c4a1181 100644
> > --- a/drivers/gpu/drm/i915/i915_gem_gtt.c
> > +++ b/drivers/gpu/drm/i915/i915_gem_gtt.c
> > @@ -34,25 +34,35 @@ static void gen8_setup_private_ppat(struct drm_i915_private *dev_priv);
> >  
> >  bool intel_enable_ppgtt(struct drm_device *dev, bool full)
> >  {
> > -	if (i915.enable_ppgtt == 0 || !HAS_ALIASING_PPGTT(dev))
> > +	if (i915.enable_ppgtt == 0)
> >  		return false;
> >  
> >  	if (i915.enable_ppgtt == 1 && full)
> >  		return false;
> >  
> > +	return true;
> > +}
> > +
> 
> /* i915.enable_ppgtt is read-only, so do an early pass to validate
>  * the user's requested state against the hardware/driver capabilities.
>  * We do this now so that we can print out any log messages once rather
>  * than every time we check intel_enable_ppgtt().
>  */
> > +static int sanitize_enable_ppgtt(struct drm_device *dev, int enable_ppgtt)
> > +{
> -Chris
> 
> -- 
> Chris Wilson, Intel Open Source Technology Centre

-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2014-04-23  7:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-22 20:17 [PATCH] drm/i915: Sanitize the enable_ppgtt module option once Daniel Vetter
2014-04-22 21:22 ` Chris Wilson
2014-04-23  7:18   ` Daniel Vetter [this message]
2014-04-23 17:44     ` Ben Widawsky
2014-04-23  8:37 ` Jani Nikula
2014-04-23 18:01   ` Daniel Vetter
2014-04-23 18:02   ` Daniel Vetter
2014-04-24 10:45     ` Jani Nikula
2014-04-25 13:11       ` Jani Nikula
  -- strict thread matches above, loose matches on Subject: below --
2014-04-29  9:53 Daniel Vetter
2014-04-29 10:44 ` Chris Wilson
2014-04-29 12:23   ` Alessandro Suardi
2014-04-29 14:06     ` Daniel Vetter
2014-04-29 15:48       ` Jani Nikula
2014-04-29 13:27   ` Jani Nikula

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=20140423071803.GU10722@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=alessandro.suardi@gmail.com \
    --cc=ben@bwidawsk.net \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --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