Messages in this thread |  | | Date | Tue, 27 Nov 2001 19:38:22 +0100 (CET) | From | Ingo Molnar <> | Subject | Re: smp_call_function & BH handlers |
| |
On Tue, 27 Nov 2001, Maneesh Soni wrote:
> I am working with Dipankar on Read-Copy Update, and experimenting with > smp_call_function(). We believed the comments for this routine and > faced this problem. That's why this question came. I have not yet > searched kernel sources for such places hence not sure whether there > are really such places or not.
we had similar lockup problems before, eg. TLB flushes initiated from IRQ/BH contexts - which is illegal now. Generally it's not safe to assume that every CPU is responsive to synchronous events triggered from IRQ/BH contexts. Every read_lock user is prone to this problem.
Ingo
- 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/
|  |