> On the other hand, we do have other ways to test the preempt count
> inside the scheduler. In particular, we might just move the
> "in_atomic()" check a few lines downwards, at which point we've released
> the kernel lock and explicitly disabled preemption, so at that point the
> test should be even simpler with fewer conditionals..
indeed ...
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/