From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: linux-next: build failure after merge of the tip tree (from the drm-intel tree)
Date: Tue, 5 Jul 2016 10:59:59 -0700 [thread overview]
Message-ID: <20160705175959.GW4650@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160705082512.GX30921@twins.programming.kicks-ass.net>
On Tue, Jul 05, 2016 at 10:25:12AM +0200, Peter Zijlstra wrote:
> On Tue, Jul 05, 2016 at 01:53:03PM +1000, Stephen Rothwell wrote:
> > diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
> > index d3502c0603e5..1f91f187b2a8 100644
> > --- a/drivers/gpu/drm/i915/i915_gem.c
> > +++ b/drivers/gpu/drm/i915/i915_gem.c
> > @@ -3290,7 +3290,7 @@ i915_gem_retire_work_handler(struct work_struct *work)
> > * We do not need to do this test under locking as in the worst-case
> > * we queue the retire worker once too often.
> > */
> > - if (lockless_dereference(dev_priv->gt.awake))
> > + if (/*lockless_dereference*/(dev_priv->gt.awake))
> > queue_delayed_work(dev_priv->wq,
> > &dev_priv->gt.retire_work,
> > round_jiffies_up_relative(HZ));
> > diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
> > index f6de8dd567a2..2c1926418691 100644
> > --- a/drivers/gpu/drm/i915/i915_irq.c
> > +++ b/drivers/gpu/drm/i915/i915_irq.c
> > @@ -3095,7 +3095,7 @@ static void i915_hangcheck_elapsed(struct work_struct *work)
> > if (!i915.enable_hangcheck)
> > return;
> >
> > - if (!lockless_dereference(dev_priv->gt.awake))
> > + if (!/*lockless_dereference*/(dev_priv->gt.awake))
> > return;
> >
> > /* As enabling the GPU requires fairly extensive mmio access,
>
> Right, neither case appears to include a data dependency and thus
> lockless_dereference() seems misguided.
Agreed! At first glance, this code wants READ_ONCE() rather than
lockless_dereference().
Thanx, Paul
prev parent reply other threads:[~2016-07-05 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 3:53 linux-next: build failure after merge of the tip tree (from the drm-intel tree) Stephen Rothwell
2016-07-05 3:53 ` Stephen Rothwell
2016-07-05 8:25 ` Peter Zijlstra
2016-07-05 8:25 ` Peter Zijlstra
2016-07-05 17:59 ` Paul E. McKenney [this message]
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=20160705175959.GW4650@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hpa@zytor.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.