Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Fri, 28 Jun 2019 17:59:15 +0100
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
Message-ID: <20190628165915.GB5143@lakrids.cambridge.arm.com>
References: <7ce0c077-06ef-676f-1f7b-61f3ba8589d1@codeaurora.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <7ce0c077-06ef-676f-1f7b-61f3ba8589d1@codeaurora.org>
User-Agent: Mutt/1.11.1+11 (2f07cb52) (2018-12-01)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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.