public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bryan Rittmeyer <bryanr@bryanr.org>
To: John Levon <levon@movementarian.org>
Cc: oprofile-list@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [patch] oprofile + ppc750cx perfmon
Date: Tue, 25 Mar 2003 19:50:00 -0800	[thread overview]
Message-ID: <20030326035000.GA32590@bryanr.org> (raw)
In-Reply-To: <20030325174309.GB57374@compsoc.man.ac.uk>

On Tue, Mar 25, 2003 at 05:43:09PM +0000, John Levon wrote:
> > done. patches are -v0002 at http://bryanr.org/linux/oprofile/
> 
> Looks OK, modulo some minor style issues (see doc/CodingStyle).

will fix in v0004.

> The patch seems to be out of date already though. Does the new cpu speed
> code not work OK for you (for the default event value) ?

I was lagging cvs; v0003 merges to today's tree, including the new
CPU_SPEED code. posted at the url above.

> Then you should fix this generally, instead of adding the hack you do.

agree. here's a separate patch for x86+ia64. with it, there's one
extra argument to op_do_profile, and oprofile.c no longer uses op_arch.h
the architecture code directly passes eip and irq_enabled. tested on
i686 2.4.20 and ppc 2.4.20-benh.

http://bryanr.org/linux/oprofile/op_do_profile-refactor.patch

ppc v0003 depends on this change.

> > +/* TODO: fix upper level. [op_rtc_ops in ppc/ia64] is really lame.  */
> 
> Sure.

I'll let you handle this one.

BTW how do you feel about reworking add_sysctl and remove_sysctl to move
shared code inside oprofile.c? Right now the duplication is causing
inconsistency e.g ia64/op_pmu.c "next->mode = 0700;" vs x86/op_nmi.c
"next->mode = 0755;"

-Bryan

  parent reply	other threads:[~2003-03-26  3:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-25  5:09 [patch] oprofile + ppc750cx perfmon Bryan Rittmeyer
2003-03-25  8:57 ` Bryan Rittmeyer
2003-03-25  9:45   ` Benjamin Herrenschmidt
2003-03-26  5:04     ` Bryan Rittmeyer
     [not found]   ` <20030325174309.GB57374@compsoc.man.ac.uk>
2003-03-26  3:50     ` Bryan Rittmeyer [this message]
     [not found]       ` <20030327010121.GA94874@compsoc.man.ac.uk>
2003-03-28  8:50         ` Bryan Rittmeyer
     [not found] <20030327130535.GA1132@bryanr.org>
     [not found] ` <F0BBB858-6093-11D7-BD8D-000393C30512@motorola.com>
2003-03-28  8:31   ` Bryan Rittmeyer

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=20030326035000.GA32590@bryanr.org \
    --to=bryanr@bryanr.org \
    --cc=levon@movementarian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oprofile-list@lists.sourceforge.net \
    /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