linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Neuling <mikey@neuling.org>
To: mjw@linux.vnet.ibm.com
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Resend: [PATCH] oprofile support for Power 5++
Date: Tue, 10 Jul 2007 15:31:38 -0500	[thread overview]
Message-ID: <911.1184099498@neuling.org> (raw)
In-Reply-To: <4693E7EF.4020708@linux.vnet.ibm.com>

> >
> > 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 followed that convention. 

I'm not too fussed, but if rev 4 comes out, the counters change and we
need power5+++, it's gonna look pretty silly :-)

Mikey

  reply	other threads:[~2007-07-10 20:31 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 [this message]
2007-07-10 21:07       ` Will Schmidt
2007-07-10 21:33         ` Maynard Johnson
2007-07-11 20:51           ` Olof Johansson

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=911.1184099498@neuling.org \
    --to=mikey@neuling.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mjw@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).