All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Atsushi Nemoto <anemo@mba.ocn.ne.jp>,
	djohnson+linuxmips@sw.starentnetworks.com,
	linux-mips@linux-mips.org
Subject: Re: preempt_schedule_irq missing from mfinfo[]?
Date: Wed, 6 Jul 2005 10:14:23 +0100	[thread overview]
Message-ID: <20050706091423.GD3226@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.61L.0507060952500.9536@blysk.ds.pg.gda.pl>

On Wed, Jul 06, 2005 at 09:58:50AM +0100, Maciej W. Rozycki wrote:

> > Yes, but many sleeping/scheduling (such as schedule_timeout(),
> > __down(), etc.)  are compiled without -fno-omit-frame-pointer, so
> > you can not find the caller of such functions anyway.
> 
>  Of course you can -- __builtin_return_address().  It should be enough for 
> `ps' to fetch useful data from "System.map", shouldn't it?

__builtin_return_address() is what those function could use themselves.
In this case it's about another piece of code unwinding the stackframe
until we hit a caller address that is not a scheduling function.

  Ralf

  reply	other threads:[~2005-07-06  9:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-30 15:50 preempt_schedule_irq missing from mfinfo[]? Dave Johnson
2005-06-30 18:23 ` Dave Johnson
2005-06-30 20:34   ` [PATCH] " Dave Johnson
2005-07-01  2:43 ` Atsushi Nemoto
2005-07-01 13:54   ` Dave Johnson
2005-07-02 15:59     ` Atsushi Nemoto
2005-07-05 20:03       ` Ralf Baechle DL5RB
2005-07-06  3:29         ` Atsushi Nemoto
2005-07-06  8:58           ` Maciej W. Rozycki
2005-07-06  9:14             ` Ralf Baechle [this message]
2005-07-06  9:01           ` Ralf Baechle
2005-07-12  8:28             ` Atsushi Nemoto

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=20050706091423.GD3226@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=djohnson+linuxmips@sw.starentnetworks.com \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@linux-mips.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.