public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Carsten Emde <C.Emde@osadl.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	RT <linux-rt-users@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	John Kacur <jkacur@redhat.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: [ANNOUNCE] 3.6.11.1-rt32
Date: Tue, 02 Apr 2013 05:13:40 +0200	[thread overview]
Message-ID: <515A4CE4.9050607@osadl.org> (raw)
In-Reply-To: <1364527527.10629.10.camel@gandalf.local.home>

Steven,

> I'm pleased to announce the 3.6.11.1-rt32 stable release.
Unfortunately, there is another compile error:
drivers/gpu/drm/i915/i915_gem.c: In function ‘i915_gem_wait_for_error’:
drivers/gpu/drm/i915/i915_gem.c:118:3: warning: passing argument 1 of 
‘rt_spin_lock’ from incompatible pointer type [enabled by default]
In file included from include/linux/spinlock.h:273:0,
                  from include/linux/wait.h:24,
                  from include/linux/fs.h:396,
                  from include/drm/drmP.h:47,
                  from drivers/gpu/drm/i915/i915_gem.c:28:
include/linux/spinlock_rt.h:21:24: note: expected ‘struct spinlock_t *’ 
but argument is of type ‘struct raw_spinlock_t *’
drivers/gpu/drm/i915/i915_gem.c:120:3: warning: passing argument 1 of 
‘rt_spin_unlock’ from incompatible pointer type [enabled by default]
In file included from include/linux/spinlock.h:273:0,
                  from include/linux/wait.h:24,
                  from include/linux/fs.h:396,
                  from include/drm/drmP.h:47,
                  from drivers/gpu/drm/i915/i915_gem.c:28:
include/linux/spinlock_rt.h:24:24: note: expected ‘struct spinlock_t *’ 
but argument is of type ‘struct raw_spinlock_t *’
drivers/gpu/drm/i915/i915_gem.c: In function ‘i915_gem_check_wedge’:
drivers/gpu/drm/i915/i915_gem.c:1890:3: warning: passing argument 1 of 
‘rt_spin_lock’ from incompatible pointer type [enabled by default]
In file included from include/linux/spinlock.h:273:0,
                  from include/linux/wait.h:24,
                  from include/linux/fs.h:396,
                  from include/drm/drmP.h:47,
                  from drivers/gpu/drm/i915/i915_gem.c:28:
include/linux/spinlock_rt.h:21:24: note: expected ‘struct spinlock_t *’ 
but argument is of type ‘struct raw_spinlock_t *’
drivers/gpu/drm/i915/i915_gem.c:1892:3: warning: passing argument 1 of 
‘rt_spin_unlock’ from incompatible pointer type [enabled by default]
In file included from include/linux/spinlock.h:273:0,
                  from include/linux/wait.h:24,
                  from include/linux/fs.h:396,
                  from include/drm/drmP.h:47,
                  from drivers/gpu/drm/i915/i915_gem.c:28:
include/linux/spinlock_rt.h:24:24: note: expected ‘struct spinlock_t *’ 
but argument is of type ‘struct raw_spinlock_t *’

I would propose to adopt the mechanism that Sebastian introduced in
3.8.4-rt2 (https://lkml.org/lkml/2013/3/26/600). The kernel compiles
and runs without any problem with the below patch on a system that
requires the i915 driver module.

	-Carsten.



From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: gpu/i915: don't open code these things

Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
---
  drivers/gpu/drm/i915/i915_gem.c |   10 ++--------
  1 file changed, 2 insertions(+), 8 deletions(-)

Index: linux-3.6.11.1-rt32/drivers/gpu/drm/i915/i915_gem.c
===================================================================
--- linux-3.6.11.1-rt32.orig/drivers/gpu/drm/i915/i915_gem.c
+++ linux-3.6.11.1-rt32/drivers/gpu/drm/i915/i915_gem.c
@@ -90,7 +90,6 @@ i915_gem_wait_for_error(struct drm_devic
  {
  	struct drm_i915_private *dev_priv = dev->dev_private;
  	struct completion *x = &dev_priv->error_completion;
-	unsigned long flags;
  	int ret;

  	if (!atomic_read(&dev_priv->mm.wedged))
@@ -115,9 +114,7 @@ i915_gem_wait_for_error(struct drm_devic
  		 * end up waiting upon a subsequent completion event that
  		 * will never happen.
  		 */
-		spin_lock_irqsave(&x->wait.lock, flags);
-		x->done++;
-		spin_unlock_irqrestore(&x->wait.lock, flags);
+		complete(x);
  	}
  	return 0;
  }
@@ -1884,12 +1881,9 @@ i915_gem_check_wedge(struct drm_i915_pri
  	if (atomic_read(&dev_priv->mm.wedged)) {
  		struct completion *x = &dev_priv->error_completion;
  		bool recovery_complete;
-		unsigned long flags;

  		/* Give the error handler a chance to run. */
-		spin_lock_irqsave(&x->wait.lock, flags);
-		recovery_complete = x->done > 0;
-		spin_unlock_irqrestore(&x->wait.lock, flags);
+		recovery_complete = completion_done(x);

  		/* Non-interruptible callers can't handle -EAGAIN, hence return
  		 * -EIO unconditionally for these. */



  parent reply	other threads:[~2013-04-02  3:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-29  3:25 [ANNOUNCE] 3.6.11.1-rt32 Steven Rostedt
2013-04-02  1:37 ` Carsten Emde
2013-04-11 17:50   ` Steven Rostedt
2013-04-02  3:13 ` Carsten Emde [this message]
2013-04-09 17:46   ` Steven Rostedt
2013-04-14 21:13     ` Carsten Emde
2013-04-12 15:47   ` John Kacur

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=515A4CE4.9050607@osadl.org \
    --to=c.emde@osadl.org \
    --cc=bigeasy@linutronix.de \
    --cc=jkacur@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox