From: "bibo mao" <bibo.mao@gmail.com>
To: mingo@redhat.com
Cc: anil.s.keshavamurthy@intel.com, ananth@in.ibm.com,
prasanna@in.ibm.com, systemtap@sources.redhat.com,
soshima@redhat.com, haoki@redhat.com,
yumiko.sugita.yf@hitachi.com
Subject: Re: [RFC][PATCH][kprobe] enabling booster on the preemptible kernel, take 2
Date: Wed, 01 Nov 2006 17:01:00 -0000 [thread overview]
Message-ID: <fbd277f20611010440s12788720oeaae8ad1daa3e1d6@mail.gmail.com> (raw)
I am not familiar with freeze_processes(), I only view code.
And I write simple program(though buggy) to test:
---------------------------------------
struct task_struct *g, *p;
if (freeze_processes()) {
goto Thaw;
}
do_each_thread(g, p) {
if (frozen(p))
continue;
printk("%s not stopped\n", p->comm );
} while_each_thread(g, p);
Thaw:
thaw_processes();
------------------------------------
the output is this(except for current thread):
ksoftirqd/0 not stopped
watchdog/0 not stopped
events/0 not stopped
khelper not stopped
kthread not stopped
kblockd/0 not stopped
kacpid not stopped
aio/0 not stopped
xfslogd/0 not stopped
xfsdatad/0 not stopped
kpsmoused not stopped
ipw2100/0 not stopped
it seems that many threads are not frozen even freeze_processes
return 0.
thanks
bibo,mao
"Ingo Molnar" <mingo@redhat.com> wrote:
> 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
>
>
next reply other threads:[~2006-11-01 12:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 17:01 bibo mao [this message]
2006-11-02 18:51 ` Masami Hiramatsu
2006-11-03 9:16 ` bibo,mao
2006-11-06 18:52 ` [RFC][PATCH][kprobe] enabling booster on the preemptible kernel, take 3 Masami Hiramatsu
-- strict thread matches above, loose matches on Subject: below --
2006-10-16 13:14 [RFC][PATCH][kprobe] enabling booster on the preemptible kernel, take 2 Masami Hiramatsu
2006-10-30 6:37 ` bibo,mao
2006-10-30 14:07 ` Masami Hiramatsu
2006-10-31 9:14 ` bibo,mao
2006-10-31 13:47 ` Masami Hiramatsu
2006-10-31 13:49 ` Ingo Molnar
2006-10-31 14:13 ` Ingo Molnar
2006-10-31 16:39 ` Masami Hiramatsu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fbd277f20611010440s12788720oeaae8ad1daa3e1d6@mail.gmail.com \
--to=bibo.mao@gmail.com \
--cc=ananth@in.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=haoki@redhat.com \
--cc=mingo@redhat.com \
--cc=prasanna@in.ibm.com \
--cc=soshima@redhat.com \
--cc=systemtap@sources.redhat.com \
--cc=yumiko.sugita.yf@hitachi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).