Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: djohnson+linuxmips@sw.starentnetworks.com, linux-mips@linux-mips.org
Subject: Re: preempt_schedule_irq missing from mfinfo[]?
Date: Wed, 6 Jul 2005 10:01:38 +0100	[thread overview]
Message-ID: <20050706090138.GC3226@linux-mips.org> (raw)
In-Reply-To: <20050706.122912.71087098.nemoto@toshiba-tops.co.jp>

On Wed, Jul 06, 2005 at 12:29:12PM +0900, Atsushi Nemoto wrote:

> >>>>> On Tue, 5 Jul 2005 21:03:09 +0100, Ralf Baechle <ralf@linux-mips.org> said:
> ralf> If the WCHAN column of ps axl is supposed to be any useful we
> ralf> need to unwind the stack until we find the caller of the
> ralf> sleeping or scheduling function.  Very useful for debugging.
> 
> 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.

Without additional information a framepointer isn't terribly useful on
MIPS.  Unfortunately it's stored at a non-constant offset in a function's
stackframe.

> And some sleeping/scheduling functions which are compiled with
> -fno-omit-frame-pointer are static or deprecated (sleep_on(), etc.)
> 
> You can find the caller of "schedule()" even with simple
> thread_saved_pc().  I think it is enough so I do not think it is worth
> to fix (and maintain) current minfo[].

The alternative would be to finally bite the bullet and add a wchan field
to thread_struct and initialize it in all the sleeping functions.

The IA-64 people have something like a DWARF-based frame unwinder but
that just seems to heavy.

  Ralf

  parent reply	other threads:[~2005-07-06  9:01 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
2005-07-06  9:01           ` Ralf Baechle [this message]
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=20050706090138.GC3226@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 \
    /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