> code. This is the reason I changed synchronize_bh, to handle also the case
> in which one CPU is running disable_bh in a irq handler... (and because I
> can' t understand why we can't run wait_on_bh from an irq handler..).
Ah, understood, the reason for not blocking in synchronize_bh inside an
irq handler is to avoid deadlocking if both the irq handler and the
previous kernel code are running start_bh_atomic()...
Andrea Arcangeli
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/