mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Mukesh Ojha <mojha@codeaurora.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Perf framework : Cluster based counter support
Date: Mon, 1 Jul 2019 17:37:13 +0100	[thread overview]
Message-ID: <20190701163712.GC31063@lakrids.cambridge.arm.com> (raw)
In-Reply-To: <aca3b787-af8d-79fb-c23f-38accdd5d4e0@codeaurora.org>

On Mon, Jul 01, 2019 at 09:09:33PM +0530, Mukesh Ojha wrote:
> 
> On 6/28/2019 10:29 PM, Mark Rutland wrote:
> > On Fri, Jun 28, 2019 at 10:23:10PM +0530, Mukesh Ojha wrote:
> > > Hi All,
> > Hi Mukesh,
> > 
> > > Is it looks considerable to add cluster based event support to add in
> > > current perf event framework and later in userspace perf to support
> > > such events ?
> > Could you elaborate on what you mean by "cluster based event"?
> > 
> > I assume you mean something like events for a cluster-affine shared
> > resource like some level of cache?
> > 
> > If so, there's a standard pattern for supporting such system/uncore
> > PMUs, see drivers/perf/qcom_l2_pmu.c and friends for examples.
> 
> Thanks Mark for pointing it out.
> Also What is stopping us in adding cluster based event e.g L2 cache hit/miss
> or some other type raw events  in core framework ?

That depends on how the event is exposed.

If it's exposed via the architectural PMU, then it's already accessible
as a raw (cpu-affine) event, regardless of whether that makes sense.

If it's a separate PMU (as I suspect is the case), then it simply has to
be a separate PMU driver.

Thanks,
Mark.

      reply	other threads:[~2019-07-01 16:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-28 16:53 Mukesh Ojha
2019-06-28 16:59 ` Mark Rutland
2019-07-01 15:39   ` Mukesh Ojha
2019-07-01 16:37     ` Mark Rutland [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=20190701163712.GC31063@lakrids.cambridge.arm.com \
    --to=mark.rutland@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mojha@codeaurora.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

all inboxes | Powered by JetHome®