All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] drm/i915: correct lock type in destroy
@ 2012-01-23 23:30 Ben Widawsky
  2012-01-24  5:20 ` Keith Packard
  2012-01-26 10:31 ` Daniel Vetter
  0 siblings, 2 replies; 3+ messages in thread
From: Ben Widawsky @ 2012-01-23 23:30 UTC (permalink / raw)
  To: intel-gfx; +Cc: Ben Widawsky

This is only relevant when using module unloading, and really only helps
get rid of a probably benign warning.

I can't remember if I sent this out already, but it's not turning up in
any of my searches.

Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
---
 drivers/gpu/drm/i915/i915_irq.c |    5 +++--
 1 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
index 65ee789..d71c0a5 100644
--- a/drivers/gpu/drm/i915/i915_irq.c
+++ b/drivers/gpu/drm/i915/i915_irq.c
@@ -1016,11 +1016,12 @@ void i915_destroy_error_state(struct drm_device *dev)
 {
 	struct drm_i915_private *dev_priv = dev->dev_private;
 	struct drm_i915_error_state *error;
+	unsigned long flags;
 
-	spin_lock(&dev_priv->error_lock);
+	spin_lock_irqsave(&dev_priv->error_lock, flags);
 	error = dev_priv->first_error;
 	dev_priv->first_error = NULL;
-	spin_unlock(&dev_priv->error_lock);
+	spin_unlock_irqrestore(&dev_priv->error_lock, flags);
 
 	if (error)
 		i915_error_state_free(dev, error);
-- 
1.7.7.2

^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCH] drm/i915: correct lock type in destroy
  2012-01-23 23:30 [PATCH] drm/i915: correct lock type in destroy Ben Widawsky
@ 2012-01-24  5:20 ` Keith Packard
  2012-01-26 10:31 ` Daniel Vetter
  1 sibling, 0 replies; 3+ messages in thread
From: Keith Packard @ 2012-01-24  5:20 UTC (permalink / raw)
  To: intel-gfx; +Cc: Ben Widawsky


[-- Attachment #1.1: Type: text/plain, Size: 583 bytes --]

On Mon, 23 Jan 2012 15:30:02 -0800, Ben Widawsky <ben@bwidawsk.net> wrote:
> This is only relevant when using module unloading, and really only helps
> get rid of a probably benign warning.
> 
> I can't remember if I sent this out already, but it's not turning up in
> any of my searches.

I haven't seen it before. I reviewed all of our other spinlocks and it
looks like this is the only error of this kind (using a spinlock in both
irq and non-irq versions).

Reviewed-by: Keith Packard <keithp@keithp.com>

I'll pull this into -fixes

-- 
keith.packard@intel.com

[-- Attachment #1.2: Type: application/pgp-signature, Size: 827 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] drm/i915: correct lock type in destroy
  2012-01-23 23:30 [PATCH] drm/i915: correct lock type in destroy Ben Widawsky
  2012-01-24  5:20 ` Keith Packard
@ 2012-01-26 10:31 ` Daniel Vetter
  1 sibling, 0 replies; 3+ messages in thread
From: Daniel Vetter @ 2012-01-26 10:31 UTC (permalink / raw)
  To: Ben Widawsky; +Cc: intel-gfx

On Mon, Jan 23, 2012 at 03:30:02PM -0800, Ben Widawsky wrote:
> This is only relevant when using module unloading, and really only helps
> get rid of a probably benign warning.
> 
> I can't remember if I sent this out already, but it's not turning up in
> any of my searches.
> 
> Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
Only developers use module unload anyway, and we shouldn't have anything
left running that might take this look from irq context. So queued for
-next, thanks for the patch.
-Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2012-01-26 10:31 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-01-23 23:30 [PATCH] drm/i915: correct lock type in destroy Ben Widawsky
2012-01-24  5:20 ` Keith Packard
2012-01-26 10:31 ` Daniel Vetter

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.