public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Levon <levon@movementarian.org>
To: Akinobu Mita <amgta@yacht.ocn.ne.jp>
Cc: phil.el@wanadoo.fr, linux-kernel@vger.kernel.org, gnb@melbourne.sgi.com
Subject: Re: [mm patch] oprofile: backtrace operation does not initialized
Date: Wed, 8 Dec 2004 16:00:55 +0000	[thread overview]
Message-ID: <20041208160055.GA82465@compsoc.man.ac.uk> (raw)
In-Reply-To: <200412081830.51607.amgta@yacht.ocn.ne.jp>

On Wed, Dec 08, 2004 at 06:30:51PM +0900, Akinobu Mita wrote:

> When I forced the oprofile to use timer interrupt with specifying
> "timer=1" module parameter. "oprofile_operations->backtrace" did
> not initialized on i386.
> 
> Please apply this patch, or make oprofile initialize the backtrace
> operation in case of using timer interrupt in your preferable way.

I don't like this patch. The arches should just set the backtrace
always, then try to init the hardware. oprofile_init() should then force
the timer ops as needed.

Greg?

john

  parent reply	other threads:[~2004-12-08 16:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-08  9:30 [mm patch] oprofile: backtrace operation does not initialized Akinobu Mita
2004-12-08  9:34 ` Akinobu Mita
2004-12-08 11:13   ` Ingo Molnar
2004-12-08 11:37     ` Akinobu Mita
2004-12-08 16:00 ` John Levon [this message]
2004-12-08 22:31   ` Greg Banks
2004-12-08 23:56     ` Philippe Elie
2004-12-09  0:39       ` Greg Banks
2004-12-09  1:46         ` John Levon
2004-12-09  1:50           ` Greg Banks
2004-12-09  2:23             ` John Levon
2004-12-09 14:22             ` Akinobu Mita
2004-12-09 14:53               ` Akinobu Mita
2004-12-09 14:55                 ` John Levon
2004-12-09 15:27                   ` Greg Banks
2004-12-09 15:23               ` Greg Banks

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=20041208160055.GA82465@compsoc.man.ac.uk \
    --to=levon@movementarian.org \
    --cc=amgta@yacht.ocn.ne.jp \
    --cc=gnb@melbourne.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phil.el@wanadoo.fr \
    /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