Messages in this thread | | | Date | Sun, 13 Oct 2002 20:38:38 +0200 | From | Pavel Machek <> | Subject | in_atomic() & spin_lock / spin_unlock in different functions |
| |
Hi!
What is it that in_atomic counts? Obviously spinlocks and get_cpu/put_cpu. Anything else?
Is there easy way to find out which spinlock causes "scheduling in atomic" warning? [It happens a *lot* in swsusp].
I'm doing spin_lock_irqsave() then in another function spin_unlock_irqrestore. Is that okay? If no, can it cause "scheduling in atomic"? Pavel -- When do you have heart between your knees? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |