All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Maynard Johnson <maynardj@us.ibm.com>
Cc: willschm@linux.vnet.ibm.com, linuxppc-dev@ozlabs.org,
	Michael Neuling <mikey@neuling.org>,
	mjw@linux.vnet.ibm.com
Subject: Re: Resend: [PATCH] oprofile support for Power 5++
Date: Wed, 11 Jul 2007 15:51:40 -0500	[thread overview]
Message-ID: <20070711205140.GA7298@lixom.net> (raw)
In-Reply-To: <4693FB3C.4060305@us.ibm.com>

On Tue, Jul 10, 2007 at 04:33:48PM -0500, Maynard Johnson wrote:
> Will Schmidt wrote:
> 
> > On Tue, 2007-07-10 at 15:31 -0500, Michael Neuling wrote:
> > 
> >>>>Does it make more sense to call this "ppc64/power5+rev3"?  
> >>>>  
> >>>
> >>>This is a change to support new counter setup for oprofile.  It may be the
> >>>same if there is a revision 4 or 5 etc.  So since the internal name was ++
> I have no idea if there will be a revision 4, etc, but I'm assuming the 
> behavior would be the same as rev 3.  So I'm not in favor of changing 

The way the cputable patch is now, the rev 4 would match the base revision
anyway.  Maybe it makes more sense to make PVR xxxx01xx and xxxx02xx
explicitly match the old power5+, and make everything else match power5++?

I guess it all depends on the chance of IBM doing another major rev of
power5. Given it's current phase of product maturity I suppose it's not
all that likely. Doing it this way saves yet another cputable entry as
well, since it would otherwise mean two added entries instead of one.


-Olof

      reply	other threads:[~2007-07-11 20:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-10 18:13 Resend: [PATCH] oprofile support for Power 5++ Mike Wolf
2007-07-10 19:43 ` Michael Neuling
2007-07-10 20:11   ` Mike Wolf
2007-07-10 20:31     ` Michael Neuling
2007-07-10 21:07       ` Will Schmidt
2007-07-10 21:33         ` Maynard Johnson
2007-07-11 20:51           ` Olof Johansson [this message]

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=20070711205140.GA7298@lixom.net \
    --to=olof@lixom.net \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=maynardj@us.ibm.com \
    --cc=mikey@neuling.org \
    --cc=mjw@linux.vnet.ibm.com \
    --cc=willschm@linux.vnet.ibm.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.