This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: [RFC][PATCH][kprobe] enabling booster on the preemptible kernel, take 2
- From: Ingo Molnar <mingo at redhat dot com>
- To: Masami Hiramatsu <masami dot hiramatsu dot pt at hitachi dot com>
- Cc: "bibo,mao" <bibo_mao at linux dot intel dot com>, "bibo,mao" <bibo dot mao at intel dot com>, "Keshavamurthy, Anil S" <anil dot s dot keshavamurthy at intel dot com>, Ananth N Mavinakayanahalli <ananth at in dot ibm dot com>, Prasanna S Panchamukhi <prasanna at in dot ibm dot com>, SystemTAP <systemtap at sources dot redhat dot com>, Satoshi Oshima <soshima at redhat dot com>, Hideo Aoki <haoki at redhat dot com>, Yumiko Sugita <yumiko dot sugita dot yf at hitachi dot com>
- Date: Tue, 31 Oct 2006 14:47:21 +0100
- Subject: Re: [RFC][PATCH][kprobe] enabling booster on the preemptible kernel, take 2
- References: <45338593.6090207@hitachi.com> <45459D94.8060905@intel.com> <454606EC.1030807@hitachi.com> <4546BCE7.9030008@linux.intel.com> <45474CDB.3080705@hitachi.com>
On Tue, 2006-10-31 at 22:17 +0900, Masami Hiramatsu wrote:
> OK, I see.
> It seems problematic because the softirqd is PF_NOFREEZE and it
> can execute most of functions...
> I think we need to find a new way to solve this problem.
could you outline the problem to me? freeze_processes() should be a
generic facility to move all kernel processing into a 'known' context of
execution. All the PF_NOFREEZE kernel threads are supposed to do
periodic calls to try_to_freeze(). They should not (and most of the time
they do not) prevent freezing of all state on the system.
am i misunderstanding the problem?
Ingo