From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: 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: Tue, 29 Apr 2014 16:27:15 +0300 [thread overview]
Message-ID: <87iopstgek.fsf@intel.com> (raw)
In-Reply-To: <20140429104450.GB23841@nuc-i3427.alporthouse.com>
On Tue, 29 Apr 2014, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Tue, Apr 29, 2014 at 11:53:58AM +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
>>
>> 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.
>>
>> v2:
>> - Add comment and pimp commit message (Chris)
>> - Use the param consistently (Jani)
>>
>> v3:
>> - Fix init sequence on pre-gen6 by moving the sanitize_ppgtt call to
>> gtt_init. Fixes boot hangs on pre-gen6.
>> - Add a debug output for the sanitize ppgtt mode.
>>
>> References: https://lkml.org/lkml/2014/4/17/599
>> Rererences: https://bugs.freedesktop.org/show_bug.cgi?id=77916
>> Cc: Alessandro Suardi <alessandro.suardi@gmail.com>
>> Cc: Ben Widawsky <ben@bwidawsk.net>
>> Cc: Chris Wilson <chris@chris-wilson.co.uk>
>> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>
> I am pretty sure we only call i915_gem_gtt_init() once during driver
> load... So let's try that r-b again.
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Pushed to -fixes, thanks for the patch and review.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-04-29 13:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 9:53 [PATCH] drm/i915: Sanitize the enable_ppgtt module option once 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-22 20:17 Daniel Vetter
2014-04-22 21:22 ` Chris Wilson
2014-04-23 7:18 ` Daniel Vetter
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
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=87iopstgek.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--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