From: Jens Axboe <axboe@kernel.dk>
To: "Syrjala, Ville" <ville.syrjala@linux.intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jani Nikula <jani.nikula@linux.intel.com>,
Dave Airlie <airlied@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Subject: Re: [PATCH] drm/i915: Make vblank evade warnings optional
Date: Mon, 8 May 2017 09:19:08 -0600 [thread overview]
Message-ID: <dee6e31a-9950-bfbf-1dec-7b8fedb30efd@kernel.dk> (raw)
In-Reply-To: <20170508072536.pgassg5phmx2a6mg@phenom.ffwll.local>
On 05/08/2017 01:25 AM, Daniel Vetter wrote:
> On Sun, May 07, 2017 at 07:52:14PM -0600, Jens Axboe wrote:
>> On 05/07/2017 11:56 AM, Daniel Vetter wrote:
>>> On Sun, May 7, 2017 at 7:46 PM, Jens Axboe <axboe@kernel.dk> wrote:
>>>> On 05/07/2017 11:12 AM, ville.syrjala@linux.intel.com wrote:
>>>>> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>>>>>
>>>>> Add a new Kconfig option to enable/disable the extra warnings
>>>>> from the vblank evade code. For now we'll keep the warning
>>>>> about an actually missed vblank always enabled as that can have
>>>>> an actual user visible impact. But if we miss the deadline
>>>>> othrwise there's no real need to bother the user with that.
>>>>> We'll want these warnings enabled during development however
>>>>> so that we can catch regressions.
>>>>>
>>>>> Based on the reports it looks like this is still very easy
>>>>> to hit on SKL, so we have more work ahead of us to optimize
>>>>> the crtiical section further.
>>>>
>>>> Shouldn't it just be a debug printk or something instead, so that normal
>>>> people don't see it, but the folks that turn on debugging can get the
>>>> info they need? Seems silly to add a kconfig option for this.
>>>
>>> I guess we could keep it as debug for users, but we want to make this
>>> a hard failure on our CI machines. Kconfig knob is the easiest to roll
>>> out to all machines.
>>
>> Wouldn't a module parameter be more useful then, as an opt-in
>> to catch these violations.
>>
>> Nobody is going to know wtf to set this kconfig option to.
>
> They're all hidden behind an overall i915 debugging option which tells you
> not to enable it. You won't see this.
OK, that does improve things a bit.
--
Jens Axboe
next prev parent reply other threads:[~2017-05-08 15:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 3:44 [git pull] drm pull for v4.12 Dave Airlie
2017-05-06 20:02 ` Linus Torvalds
2017-05-07 12:33 ` Daniel Vetter
2017-05-07 17:12 ` [PATCH] drm/i915: Make vblank evade warnings optional ville.syrjala
2017-05-07 17:46 ` Jens Axboe
2017-05-07 17:56 ` Daniel Vetter
2017-05-08 1:52 ` Jens Axboe
2017-05-08 7:25 ` Daniel Vetter
2017-05-08 15:19 ` Jens Axboe [this message]
2017-05-08 7:26 ` 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=dee6e31a-9950-bfbf-1dec-7b8fedb30efd@kernel.dk \
--to=axboe@kernel.dk \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=torvalds@linux-foundation.org \
--cc=ville.syrjala@linux.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 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).