http://bugs.freedesktop.org/show_bug.cgi?id=14937





--- Comment #3 from Mike Isely <[EMAIL PROTECTED]>  2008-04-13 01:41:39 PST ---
Interesting.  I was unaware of spin_lock_bh(), but having looked at it now I
agree.  If I had seen it before, I would have used it.

But for what it's worth, I didn't use spin_lock_irqsave() without some care
first.   This spin lock is only ever taken for very short reasonably
deterministic, non-blocking intervals in the DRM code (as part of taking a much
heavier-weight lock).  So I felt that any latency impact from interrupt
blockage in these cases should be negligible and thus I didn't really look for
a different (potentially more complex solution).

  -Mike


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
--
_______________________________________________
Dri-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to