public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@engr.sgi.com>
To: Andi Kleen <ak@suse.de>
Cc: bcasavan@sgi.com, linux-kernel@vger.kernel.org, rusty@rustcorp.com.au
Subject: Re: [PATCH] Add kallsyms_lookup() result cache
Date: Fri, 18 Jun 2004 20:16:48 -0400	[thread overview]
Message-ID: <200406182016.48376.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <20040619015652.232b3b55.ak@suse.de>

On Friday, June 18, 2004 7:56 pm, Andi Kleen wrote:
> > Sure, but that would be a change in behavior.  It's arguably the right
> > thing to do though.
>
> Change what behaviour? I argue that doing it in the kernel is the wrong
> thing.

/proc/<pid>/wchan reports the function name as a string.  You're arguing that 
doing that in the kernel is the wrong thing to do, right?  If so, it would 
make sense to change its behavior.  Either way, I guess we can fix top to 
use /proc/<pid>/stat instead, and lookup symbols in an external System.map 
file.

Jesse

  reply	other threads:[~2004-06-19  0:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-18 20:03 [PATCH] Add kallsyms_lookup() result cache Brent Casavant
2004-06-18 20:37 ` Martin Josefsson
2004-06-18 20:55   ` Brent Casavant
2004-06-18 22:03 ` Andi Kleen
2004-06-18 23:26   ` Jesse Barnes
2004-06-18 23:56     ` Andi Kleen
2004-06-19  0:16       ` Jesse Barnes [this message]
2004-06-18 23:31   ` Brent Casavant
2004-06-18 23:59     ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2004-06-19  0:43 Albert Cahalan
2004-06-19  4:51 ` Herbert Xu
2004-06-19 12:03   ` Albert Cahalan
2004-06-19 10:06 ` Andrew Morton
2004-06-19 13:05   ` Albert Cahalan
2004-06-22 19:45     ` Brent Casavant
2004-06-22 20:10       ` Jesse Barnes

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=200406182016.48376.jbarnes@engr.sgi.com \
    --to=jbarnes@engr.sgi.com \
    --cc=ak@suse.de \
    --cc=bcasavan@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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