public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom•net>
To: Mike Wolf <mjw@linux•vnet.ibm.com>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: [PATCH] powerpc: adjust oprofile_cpu_type
Date: Thu, 23 Apr 2009 17:09:09 -0500	[thread overview]
Message-ID: <20090423220909.GA10487@lixom.net> (raw)
In-Reply-To: <1240523816.12000.2.camel@mx3>

On Thu, Apr 23, 2009 at 04:56:56PM -0500, Mike Wolf wrote:
> On Thu, 2009-04-23 at 12:52 -0500, Olof Johansson wrote:
> > On Wed, Apr 22, 2009 at 06:40:12PM -0500, Mike Wolf wrote:
> > > Resending.  the patch was munged last time.
> > > 
> > > 
> > > Oprofile is changing the naming it is using for the compatibility modes.
> > > Instead of having compat-power<x>, oprofile will go to family naming
> > > convention and use compat-v<x>.  Currently only compat-v1 will be
> > > defined.
> > 
> > Compat V1 of what? powerpc64? IBM powerpc64 PMC? 
> 
> IBM powerpc PMC

Sounds like it'd be appropriate to have an ibm somewhere in the version
string then.

> >  The performance
> > monitors are not architected, to give them a version number without
> > vendor information seems weird.
> The current ones all fall into one family and they may be architected in
> the future.

Not all powerpc PMC implementations do, not even all ppc64 ones --
PA6T implements a completely different performance monitor.

The current IBM PMC is included in the appendix of the architecture as
a suggestion on how to implement it, but it is explicitly specified
as being implementation dependent in the architecture.

> > Also, doesn't this break compatibility with existing userspace tools?
> AFAIK there is nothing else that uses these.  Oprofile patch was
> rejected and this new naming was suggested from that community.

Ok, as long as you are 100% sure there are no proprietary users either.


-Olof

  reply	other threads:[~2009-04-23 22:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-22 23:40 [PATCH] powerpc: adjust oprofile_cpu_type Mike Wolf
2009-04-23  3:47 ` Kumar Gala
2009-04-23 17:52 ` Olof Johansson
2009-04-23 21:56   ` Mike Wolf
2009-04-23 22:09     ` Olof Johansson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-04-17 19:48 Mike Wolf

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=20090423220909.GA10487@lixom.net \
    --to=olof@lixom$(echo .)net \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=mjw@linux$(echo .)vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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