Re: [RFC][PATCH 0/5] Introduce checks for preemptable code for this_cpu_read/write()

From: Andi Kleen
Date: Mon Sep 19 2011 - 22:20:33 EST


Steven Rostedt <rostedt@xxxxxxxxxxx> writes:

> I just found out that the this_cpu_*() functions do not perform the
> test to see if the usage is in atomic or not. Thus, the blind
> conversion of the per_cpu(*, smp_processor_id()) and the get_cpu_var()
> code to this_cpu_*() introduce the regression to detect the hard
> to find case where a per cpu variable is used in preempt code that
> migrates and causes bugs.


Didn't preempt-rt recently get changed to not migrate in kernel-preempt
regions. How about just fixing the normal preemption to not do this
either.

Then all these complications wouldn't be necessary and a whole lot
of code related to this could be removed too, and you would still
have less bugs.

-Andi

--
ak@xxxxxxxxxxxxxxx -- Speaking for myself only
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/