From: "Luis Claudio R. Goncalves" <lclaudio@uudg.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
Sebastian Sewior <bigeasy@linutronix.de>
Subject: Re: [ANNOUNCE] 3.8.4-rt1
Date: Fri, 22 Mar 2013 22:30:03 -0300 [thread overview]
Message-ID: <20130323013003.GU11538@uudg.org> (raw)
In-Reply-To: <alpine.LFD.2.02.1303222301010.22263@ionos>
On Fri, Mar 22, 2013 at 11:10:11PM +0100, Thomas Gleixner wrote:
| Dear RT Folks,
|
| I'm pleased to announce the 3.8.4-rt1 release.
|
| Again the credit for the heavy lifting goes to Sebastian Siewior, AKA
| bigeasy, who took up most of the work to get this out. He's on my
| companies engineering team and I hope you trust him as much as I do.
|
| Known issues:
|
| - SLUB behaves worse than SLAB on ARM
| - SLAB is broken on PowerPC
|
| Still we think that it's time to get out the stuff for broader
| testing. It's -rt1 and we need your help to get this stabilized.
Thomas, in order to build 3.8.4-rt1 I had to apply this little chenge:
As struct completion has a raw_spin_lock, we need to use the matching
(raw_*) locking funtions.
diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
index de45b60..817e60b 100644
--- a/drivers/gpu/drm/i915/i915_gem.c
+++ b/drivers/gpu/drm/i915/i915_gem.c
@@ -116,9 +116,9 @@ i915_gem_wait_for_error(struct drm_device *dev)
* end up waiting upon a subsequent completion event that
* will never happen.
*/
- spin_lock_irqsave(&x->wait.lock, flags);
+ raw_spin_lock_irqsave(&x->wait.lock, flags);
x->done++;
- spin_unlock_irqrestore(&x->wait.lock, flags);
+ raw_spin_unlock_irqrestore(&x->wait.lock, flags);
}
return 0;
}
@@ -949,9 +949,9 @@ i915_gem_check_wedge(struct drm_i915_private *dev_priv,
unsigned long flags;
/* Give the error handler a chance to run. */
- spin_lock_irqsave(&x->wait.lock, flags);
+ raw_spin_lock_irqsave(&x->wait.lock, flags);
recovery_complete = x->done > 0;
- spin_unlock_irqrestore(&x->wait.lock, flags);
+ raw_spin_unlock_irqrestore(&x->wait.lock, flags);
/* Non-interruptible callers can't handle -EAGAIN, hence return
* -EIO unconditionally for these. */
--
[ Luis Claudio R. Goncalves Bass - Gospel - RT ]
[ Fingerprint: 4FDD B8C4 3C59 34BD 8BE9 2696 7203 D980 A448 C8F8 ]
next prev parent reply other threads:[~2013-03-23 1:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 22:10 [ANNOUNCE] 3.8.4-rt1 Thomas Gleixner
2013-03-23 1:30 ` Luis Claudio R. Goncalves [this message]
2013-03-23 17:17 ` cpufreq + PREEMPT_RT_FULL give bad context sleeping BUG Gregoire Gentil
2013-03-26 20:51 ` Sebastian Andrzej Siewior
2013-03-26 21:07 ` Thomas Gleixner
2013-03-26 21:33 ` Sebastian Andrzej Siewior
2013-03-26 21:38 ` Thomas Gleixner
2013-03-26 21:44 ` Thomas Gleixner
2013-03-27 15:23 ` Gregoire Gentil
2013-04-25 15:23 ` Sebastian Andrzej Siewior
2013-03-23 18:38 ` [ANNOUNCE] 3.8.4-rt1 Sebastian Andrzej Siewior
2013-03-24 1:15 ` Luis Claudio R. Goncalves
2013-03-23 3:31 ` Luis Claudio R. Goncalves
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=20130323013003.GU11538@uudg.org \
--to=lclaudio@uudg.org \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).