Hello Tejun Heo,
I've backported the schedule_on_each_cpu() "direct excution" patch on
3.0.30-rt50,
and It fixed my problem.
attachment is the effective patch.
However, I do not understand why machine1 can expose problem, but
machine2 not.
I guess, because it's rt-kernel's preempt
ng up executing the function twice on the new cpu but skipping the
old one.
does this situation will happen in "Full preemption" config, on 3.0.30-rt50?
于 2013年06月07日 09:34, we...@kylinos.com.cn 写道:
it's preemption mode related ,
on the 3.0.30-rt50, only config kernel
it's preemption mode related ,
on the 3.0.30-rt50, only config kernel with highest preemption level
(Fully Preemptible Kernel (RT)) in cpu preemption model
will cause problem
and even i use the "Preemptible Kernel" or "Preemptible Kernel
(Low-Latency Desktop)" the problem would not happen
3 matches
Mail list logo