linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis Claudio R. Goncalves" <lclaudio@uudg.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] 3.8.4-rt1
Date: Sat, 23 Mar 2013 22:15:53 -0300	[thread overview]
Message-ID: <20130324011553.GA3184@uudg.org> (raw)
In-Reply-To: <20130323183827.GA31738@linutronix.de>

On Sat, Mar 23, 2013 at 07:38:27PM +0100, Sebastian Andrzej Siewior wrote:
| * Luis Claudio R. Goncalves | 2013-03-22 22:30:03 [-0300]:
| 
| What about this:
| 
| diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
| index de45b60..9b51712 100644
| --- a/drivers/gpu/drm/i915/i915_gem.c
| +++ b/drivers/gpu/drm/i915/i915_gem.c
| @@ -91,7 +91,6 @@ i915_gem_wait_for_error(struct drm_device *dev)
|  {
|  	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))
| @@ -116,9 +115,7 @@ 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);
| -		x->done++;
| -		spin_unlock_irqrestore(&x->wait.lock, flags);
| +		complete(x);
|  	}
|  	return 0;
|  }
| @@ -946,12 +943,9 @@ i915_gem_check_wedge(struct drm_i915_private *dev_priv,
|  	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. */

Good catch. The resulting code is cleaner. I took the simplest approach while
trying to fix the issue, but your solution is more elegant.

| @@ -4366,7 +4360,7 @@ static bool mutex_is_locked_by(struct mutex *mutex, struct task_struct *task)
|  	if (!mutex_is_locked(mutex))
|  		return false;
|  
| -#if defined(CONFIG_SMP) || defined(CONFIG_DEBUG_MUTEXES)
| +#if (defined(CONFIG_SMP) || defined(CONFIG_DEBUG_MUTEXES)) && !defined(CONFIG_PREEMPT_RT_BASE)
|  	return mutex->owner == task;
|  #else
|  	/* Since UP may be pre-empted, we cannot assume that we own the lock */

I was trying to keep the behavior of CONFIG_DEBUG_MUTEXES, but we do have
the RT counterpart, CONFIG_DEBUG_RT_MUTEXES. So, yours is probably the
right one.

| I'm not very happy with the complete() here, I am not sure what kind of
| problem they try to solve here…

I was looking at the code and IMHO it seems to fit there perfectly.

Cheers,
Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2013-03-24  1:16 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
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 [this message]
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=20130324011553.GA3184@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).