|
From: Mathieu D. <co...@kr...> - 2010-01-29 17:13:26
|
* Masami Hiramatsu (mhi...@re...) wrote: > Ingo Molnar wrote: > > > > * Masami Hiramatsu <mhi...@re...> wrote: > > > >> Disable kprobe booster when CONFIG_PREEMPT=y, because it can't ensure that > >> all kernel threads preempted on kprobe's boosted slot run out from the slot > >> even using freeze_processes(). > > > > hm, this really sucks as it makes preemptible kernels perform worse. Is there > > no better solution? > > > >> The booster on preemptive kernel will be resumed if synchronize_tasks() or > >> something like that is introduced. > > > > such as this one? > > Yes, I think this synchronize_tasks(), which just (sleeping) wait until > all currently preempted tasks are wake up and scheduled, can ensure safety If a task is set as stopped, and the preempted before calling schedule, can this result in a preempted task staying in that state for an arbitrary long period of time ? Or is there some mechanism prohibiting that in the scheduler ? Thanks, Mathieu > > Thank you, > > -- > Masami Hiramatsu > > Software Engineer > Hitachi Computer Products (America), Inc. > Software Solutions Division > > e-mail: mhi...@re... > -- Mathieu Desnoyers OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68 |