[Intel-gfx] [PATCH 7/9] drm/i915: allow package C8+ states on Haswell (disabled)
Daniel Vetter
daniel at ffwll.ch
Sat Aug 10 09:55:14 CEST 2013
On Fri, Aug 9, 2013 at 11:34 PM, Paulo Zanoni <przanoni at gmail.com> wrote:
> 2013/8/9 Chris Wilson <chris at chris-wilson.co.uk>:
>> Quick note...
>>
>> On Fri, Aug 09, 2013 at 05:10:05PM -0300, Paulo Zanoni wrote:
>>> + WARN_ON(!mutex_is_locked(&dev_priv->pc8.lock));
>>
>> Preferred form is now lockdep_assert_held(&dev_priv->pc8.lock);
>
> Should I also convert all our other usages of
> WARN_ON(!mutex_is_locked()) and BUG_ON(!mutex_is_locked()) too? On a
> separate patch, of course. We have currently no usage of
> lockdep_assert_held, and I like consistency, so fully switching to the
> preferred form is good IMHO.
Tbh I don't understand really why lockdep_assert_held is better ...
it's right that it also checks that indeed the current task is holding
the lock (and not some random other imposter). But the downside is
that it's a noop without CONFIG_PROVE_LOCKING. And due to the massive
perf impact of that option not many people actually run with it. At
least I tend to only enable it when doing tricky locking work on my
dev machines and not in general ...
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
More information about the Intel-gfx
mailing list