All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Shanthi Kiran Pendyala (skiranp)" <skiranp@cisco.com>
Cc: linux-mips <linux-mips@linux-mips.org>
Subject: Re: Oprofile on sibyte 2.4.18 kernel
Date: Sat, 8 Apr 2006 00:20:08 +0100	[thread overview]
Message-ID: <20060407232008.GB26104@linux-mips.org> (raw)
In-Reply-To: <5547014632ED654F971D7E1E0C2E0C3E018DAFBB@xmb-sjc-215.amer.cisco.com>

On Fri, Apr 07, 2006 at 01:38:54PM -0700, Shanthi Kiran Pendyala (skiranp) wrote:

> Did anyone port oprofile to 2.4.x kernel on sibyte ?.
> 
> Looking over the mailing list threads it looks like it has been given up
> as a lost cause.

Correct.  So if at all you would have to rip oprofile from the 2.6 kernel
and bolt that code back into the old kernel which would seem doable.  The
MIPS bits certainly don't rely on much 2.6 infrastructure.

> But business reasons require us to work with 2.4.18 kernel for the next
> 9-12 months and We really would like explore a port.

You at least want a newer 2.4 variant; 2.4.18 is now over 4 years old, is
from before the point where 2.4 really became stable and contains a number
of security revelant holes.

> Or are there other tools that I can use ?

Gprof, perfex 2 - not sure if the MIPS port of it was ever published though.
But nothing really that provides the same kind of information as oprofile.

  Ralf

  reply	other threads:[~2006-04-07 23:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-07 20:38 Oprofile on sibyte 2.4.18 kernel Shanthi Kiran Pendyala (skiranp)
2006-04-07 23:20 ` Ralf Baechle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-04-10 17:37 Mark E Mason
2006-04-11  1:55 Shanthi Kiran Pendyala (skiranp)
2006-04-11 21:42 Mark E Mason
2006-04-11 22:24 ` Ralf Baechle
2006-04-11 23:09 Shanthi Kiran Pendyala (skiranp)
2006-04-11 23:29 Mark E Mason

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=20060407232008.GB26104@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=skiranp@cisco.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 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.