linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jan.glauber@caviumnetworks.com (Jan Glauber)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 1/3] perf: cavium: Support memory controller PMU counters
Date: Thu, 27 Jul 2017 11:08:56 +0200	[thread overview]
Message-ID: <20170727090856.GB15784@hc> (raw)
In-Reply-To: <20170727051157.GA4525@nazgul.tnic>

On Thu, Jul 27, 2017 at 07:11:57AM +0200, Borislav Petkov wrote:
> On Wed, Jul 26, 2017 at 02:02:42PM -0700, David Daney wrote:
> > Also, if a given configuration disables CONFIG_EDAC there is some hackery
> > needed to get the perf portion of the driver included.
> 
> Yes, and we don't do performance counters in EDAC.
> 
> So you could add a small memory controller driver which does the
> arbitration or fix the firmware.

OK. As fixing the firmware will take quite some time I'll go for the memory
controller driver that starts EDAC / PMU depending on their CONFIG_.

What would be the proper location for the multiplexer?
drivers/soc/cavium or drivers/misc?

--Jan

  reply	other threads:[~2017-07-27  9:08 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-25 15:04 [PATCH v8 0/3] Cavium ARM64 uncore PMU support Jan Glauber
2017-07-25 15:04 ` [PATCH v8 1/3] perf: cavium: Support memory controller PMU counters Jan Glauber
2017-07-25 15:39   ` Suzuki K Poulose
2017-07-26 11:19     ` Jan Glauber
2017-07-26 12:47       ` Suzuki K Poulose
2017-07-26 13:10         ` Jan Glauber
2017-07-26 14:35           ` Suzuki K Poulose
2017-07-26 14:55             ` Borislav Petkov
2017-07-26 15:13               ` Jan Glauber
2017-07-26 15:17                 ` Suzuki K Poulose
2017-07-26 15:28                   ` Borislav Petkov
2017-07-26 15:46                   ` Jan Glauber
2017-07-26 16:25                     ` Jonathan Cameron
2017-07-26 16:40                       ` Jan Glauber
2017-07-26 15:35                 ` Borislav Petkov
2017-07-26 15:45                   ` Jan Glauber
2017-07-26 15:55                     ` Borislav Petkov
2017-07-26 16:19                       ` Greg KH
2017-07-26 16:30                         ` Borislav Petkov
2017-07-26 17:33                           ` Greg KH
2017-07-26 20:02                             ` David Daney
2017-07-26 20:08                               ` Greg KH
2017-07-26 21:02                                 ` David Daney
2017-07-27  2:29                                   ` Greg KH
2017-07-27 17:29                                     ` David Daney
2017-07-28  1:11                                       ` Greg KH
2017-07-28  7:23                                         ` Borislav Petkov
2017-07-27  5:11                                   ` Borislav Petkov
2017-07-27  9:08                                     ` Jan Glauber [this message]
2017-07-27 13:15                                       ` Borislav Petkov
2017-07-28 23:12                                         ` Greg KH
2017-08-08 13:25                                           ` Will Deacon
2017-08-15  9:13                                             ` Jan Glauber
2017-08-07  9:37                                       ` Suzuki K Poulose
2017-07-25 15:56   ` Jonathan Cameron
2017-07-25 15:04 ` [PATCH v8 2/3] perf: cavium: Support transmit-link " Jan Glauber
2017-07-25 15:04 ` [PATCH v8 3/3] perf: cavium: Add Documentation Jan Glauber

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=20170727090856.GB15784@hc \
    --to=jan.glauber@caviumnetworks.com \
    --cc=linux-arm-kernel@lists.infradead.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 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).