From: Christoph Hellwig <hch@infradead.org>
To: Robert Love <rml@tech9.net>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org,
riel@conectiva.com.br
Subject: Re: [PATCH] pre-decoded wchan output
Date: Thu, 17 Oct 2002 20:58:03 +0100 [thread overview]
Message-ID: <20021017205803.A7555@infradead.org> (raw)
In-Reply-To: <1034882043.1072.589.camel@phantasy>; from rml@tech9.net on Thu, Oct 17, 2002 at 03:14:02PM -0400
On Thu, Oct 17, 2002 at 03:14:02PM -0400, Robert Love wrote:
> Linus,
>
> Attached patch implements a /proc/#/wchan which provides a pre-decoded
> wchan via kallsyms. I.e.,
>
> [15:05:06]rml@phantasy:~$ cat /proc/1228/wchan
> wait4
>
> Which is damn cool to me and will let ps(1) grab wchan information
> without having to parse System.map. It also means procps will not need
> System.map.
>
> If CONFIG_KALLSYMS is enabled, /proc/#/wchan exists and exports the
> pre-decoded symbol name. The old wchan value in /proc/#/stat is
> hard-coded to zero.
>
> If CONFIG_KALLSYMS is not enabled, /proc/#/wchan does not exist to
> conserve memory. In that case, the old wchan field in /proc/#/stat will
> export the usual wchan address.
>
> This will not break procps, however the wchan field will be zero without
> an updated version if CONFIG_KALLSYMS is set. That is fine as 2.5
> requires an updated procps anyhow. If CONFIG_KALLSYMS is not set,
> things are unchanged.
Can't you just left the old, nuerical one in even if CONFIG_KALLSYMS
ise set? One ifdef less and far less surprises..
next prev parent reply other threads:[~2002-10-17 19:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 19:14 Robert Love
2002-10-17 19:58 ` Christoph Hellwig [this message]
2002-10-17 20:04 ` Robert Love
2002-10-21 23:08 ` Pavel Machek
2002-10-26 17:44 ` Robert Love
2002-10-20 22:04 ` David =?ISO-8859-1?Q?G=F3mez=22?= <david@pleyades.net>
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=20021017205803.A7555@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=rml@tech9.net \
--cc=torvalds@transmeta.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
Powered by JetHome