From: Jani Nikula <jani.nikula@linux.intel.com>
To: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH] drm/i915: Check mask/bit helper functions
Date: Mon, 08 Dec 2014 18:23:47 +0200 [thread overview]
Message-ID: <874mt6m7os.fsf@intel.com> (raw)
In-Reply-To: <877fy2m9il.fsf@intel.com>
On Mon, 08 Dec 2014, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Mon, 08 Dec 2014, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
>> After a bit of irc discussion we've concluded that it would be prudent
>> to check that callers use the mask/enable paramters correctly. So add
>> a WARN_ON.
>>
>> Spurred by Damien's bugfix which added _MASKED_FIELD.
>>
>> v2: We use WARN_ON(1) a lot to catch default cases in switch blocks
>> which should always be extended. So this doesn't work really. Dunno
>> why gcc only started complaining when I've moved the WARN out of the
>> static inline helper to address a feedback from Jani.
>
> Ah, that would be precisely because of the static inline helper. The
> function parameter is never a builtin constant!
What I learned today: This holds for -O0.
>
> BR,
> Jani.
>
>
>>
>> Cc: Damien Lespiau <damien.lespiau@intel.com>
>> Cc: Chris Wilson <chris@chris-wilson.co.uk>
>> Cc: Jani Nikula <jani.nikula@linux.intel.com>
>> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
>> ---
>> drivers/gpu/drm/i915/i915_irq.c | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
>> index 08a5a4ba52ac..e6a1db36928e 100644
>> --- a/drivers/gpu/drm/i915/i915_irq.c
>> +++ b/drivers/gpu/drm/i915/i915_irq.c
>> @@ -183,6 +183,8 @@ static void ilk_update_gt_irq(struct drm_i915_private *dev_priv,
>> {
>> assert_spin_locked(&dev_priv->irq_lock);
>>
>> + WARN_ON(enabled_irq_mask & ~interrupt_mask);
>> +
>> if (WARN_ON(!intel_irqs_enabled(dev_priv)))
>> return;
>>
>> @@ -229,6 +231,8 @@ static void snb_update_pm_irq(struct drm_i915_private *dev_priv,
>> {
>> uint32_t new_val;
>>
>> + WARN_ON(enabled_irq_mask & ~interrupt_mask);
>> +
>> assert_spin_locked(&dev_priv->irq_lock);
>>
>> new_val = dev_priv->pm_irq_mask;
>> @@ -328,6 +332,8 @@ void ibx_display_interrupt_update(struct drm_i915_private *dev_priv,
>> sdeimr &= ~interrupt_mask;
>> sdeimr |= (~enabled_irq_mask & interrupt_mask);
>>
>> + WARN_ON(enabled_irq_mask & ~interrupt_mask);
>> +
>> assert_spin_locked(&dev_priv->irq_lock);
>>
>> if (WARN_ON(!intel_irqs_enabled(dev_priv)))
>> --
>> 2.1.1
>>
>
> --
> Jani Nikula, Intel Open Source Technology Center
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-12-08 16:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 15:00 [PATCH] drm/i915: Check mask/bit helper functions Daniel Vetter
2014-12-08 15:14 ` Damien Lespiau
2014-12-08 15:19 ` Daniel Vetter
2014-12-08 15:18 ` Jani Nikula
2014-12-08 15:20 ` Daniel Vetter
2014-12-08 15:30 ` Daniel Vetter
2014-12-08 15:44 ` Jani Nikula
2014-12-08 16:23 ` Jani Nikula [this message]
2014-12-09 12:57 ` shuang.he
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=874mt6m7os.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--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