From: Keith Owens <kaos@sgi.com>
To: vinay hegde <thisismevinay@yahoo.co.in>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Need help regarding kernel threads
Date: Tue, 02 Aug 2005 19:22:50 +1000 [thread overview]
Message-ID: <11025.1122974570@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Tue, 02 Aug 2005 09:57:51 +0100." <20050802085751.55408.qmail@web8407.mail.in.yahoo.com>
On Tue, 2 Aug 2005 09:57:51 +0100 (BST),
vinay hegde <thisismevinay@yahoo.co.in> wrote:
>How to differentiate kernel threads from normal
>processes inside the Linux kernel code?
The Linux Kernel Debugger (ftp://oss.sgi.com/projects/kdb/download/v4.4)
distinguishes between idle tasks, sleeping system daemons and the rest
(typically user tasks). An idle task has pid 0, a sleeping system
daemon has a NULL mm field and is in S state, everything else is
treated as a normal task.
Download the latest kdb common patch and look at function
kdb_task_state_char.
prev parent reply other threads:[~2005-08-02 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 8:57 vinay hegde
2005-08-02 9:22 ` Keith Owens [this message]
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=11025.1122974570@kao2.melbourne.sgi.com \
--to=kaos@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thisismevinay@yahoo.co.in \
/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
Powered by JetHome