From: Tachino Nobuhiro <tachino@jp.fujitsu.com>
To: Daniel Jacobowitz <dan@debian.org>
Cc: "Vamsi Krishna S." <vamsi_krishna@in.ibm.com>,
torvalds@transmeta.com, Jeff Jenkins <jefreyr@pacbell.net>,
linux-kernel@vger.kernel.org
Subject: Re: [bkpatch] Multiple threads in core dumps (was: Re: Thread registers dumped to core-file)
Date: Tue, 12 Mar 2002 13:09:06 +0900 [thread overview]
Message-ID: <eliqqvfh.wl@nisaaru.dvs.cs.fujitsu.co.jp> (raw)
In-Reply-To: <20020309161322.A2092@nevyn.them.org>
In-Reply-To: <HFEPKLGPJDEHEGCKLKCCMEDLCCAA.jefreyr@pacbell.net> <200203090636.g296aSV273332@westrelay01.boulder.ibm.com> <20020309161322.A2092@nevyn.them.org>
Hello,
I am now trying to implement gcore system call on linux and have a
great interest in your patch.
At Sat, 09 Mar 2002 16:13:22 -0500,
Daniel Jacobowitz wrote:
>
> Here it is, against 2.5.6-pre2 (linux-2.5). I'll do a version for 2.4
> after it makes it into 2.5.
>
>
> I'm looking for feedback on this. Particularly two things:
One small feedback.
If one of the threads sleeps with TASK_UNINTERRUPTIBLE, stop_all_threads()
eats all CPU resources. I think following patch needed.
diff -ru linux-2.5-core.org/kernel/sched.c linux-2.5-core/kernel/sched.c
--- linux-2.5-core.org/kernel/sched.c Mon Mar 11 19:08:00 2002
+++ linux-2.5-core/kernel/sched.c Tue Mar 12 12:45:57 2002
@@ -763,6 +763,7 @@
if (all_stopped)
break;
read_unlock(&tasklist_lock);
+ set_current_state(TASK_UNINTERRUPTIBLE);
schedule_timeout(1);
read_lock(&tasklist_lock);
}
next prev parent reply other threads:[~2002-03-12 4:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-08 16:17 Thread registers dumped to core-file Jeff Jenkins
2002-03-09 6:45 ` Vamsi Krishna S.
2002-03-09 21:13 ` [bkpatch] Multiple threads in core dumps (was: Re: Thread registers dumped to core-file) Daniel Jacobowitz
2002-03-12 4:09 ` Tachino Nobuhiro [this message]
2002-03-12 11:07 ` [bkpatch] Multiple threads in core dumps (was: Re: Thread Tachino Nobuhiro
2002-03-12 16:42 ` Daniel Jacobowitz
2002-03-12 11:11 ` Alan Cox
2002-03-15 12:07 ` Thread registers dumped to core-file Vamsi Krishna S .
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=eliqqvfh.wl@nisaaru.dvs.cs.fujitsu.co.jp \
--to=tachino@jp.fujitsu.com \
--cc=dan@debian.org \
--cc=jefreyr@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=vamsi_krishna@in.ibm.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
all inboxes | Powered by JetHome®