On Fri, 21 Feb 2003, Thomas Schlichter wrote:
>
> So here is a minimal change patch that should solve the preempt issue in
> flush_map().
>
> Instead of just doing a preempt_disable() before and a preempt_enable()
> after
> the flush_kernel_map() calls I just changed the order so that the preempt
> point is not between them...
No. All that does is make sure that the cpu you start out on is
flushed, once or twice, and the cpu you end up on may be missed.
Use preempt_disable and preempt_enable.
Hugh
-
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/
This archive was generated by hypermail 2b29 : Sun Feb 23 2003 - 22:00:33 EST