All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <david.ahern@oracle.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH] sparc: perf: Add support M7 processor
Date: Fri, 20 Mar 2015 02:55:27 +0000	[thread overview]
Message-ID: <550B8C1F.3080508@oracle.com> (raw)
In-Reply-To: <1426795597-135713-1-git-send-email-david.ahern@oracle.com>

On 3/19/15 7:56 PM, David Miller wrote:
> Applied, but two questions:
>
> 1) Why didn't you have to deal with the overflow event
>     latching issues I address in sparc_vt_write_pmc()?

I saw the note. I need to understand why you wrote that. Relevant 
sections of the PRM for the T4 and the M7 have the same wording, so I 
was surprised to read that. Perhaps a h/w (or h/w revision) quirk?

It was not needed for the M7 -- bare metal or LDOM -- so I opted to go 
with the purist approach based on the PRM. As I get time and access to 
hardware I will take a look at the T4.

>
> 2) How simple is it to hook up a similar set of support
>     for sparc-m6?  It seems like the only PMU type string
>     we won't match after this.

Ditto. Time and H/W access.



  parent reply	other threads:[~2015-03-20  2:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19 20:06 [PATCH] sparc: perf: Add support M7 processor David Ahern
2015-03-20  1:56 ` David Miller
2015-03-20  2:55 ` David Ahern [this message]
2015-03-20 19:38 ` David Miller
2015-03-20 19:41 ` David Ahern
2015-03-20 19:50 ` David Miller
2015-04-13 17:53 ` David Ahern
2015-04-16 19:35 ` David Miller
2015-04-21 20:15 ` David Miller
2015-04-22 22:51 ` David Miller
2015-04-22 23:10 ` Khalid Aziz
2015-04-22 23:13 ` David Miller
2015-04-22 23:19 ` David Ahern
2015-04-22 23:25 ` David Miller
2015-04-22 23:30 ` Khalid Aziz
2015-04-23  0:29 ` David Ahern
2015-04-23  1:39 ` David Miller

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=550B8C1F.3080508@oracle.com \
    --to=david.ahern@oracle.com \
    --cc=sparclinux@vger.kernel.org \
    /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.