[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1801142153190.2371@nanos>
Date: Sun, 14 Jan 2018 21:53:30 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: Kan Liang <kan.liang@...el.com>
cc: peterz@...radead.org, mingo@...hat.com,
linux-kernel@...r.kernel.org, acme@...nel.org, eranian@...gle.com,
ak@...ux.intel.com
Subject: Re: [PATCH V4 7/8] perf/x86/intel/uncore: expose uncore_pmu_event
functions
On Thu, 2 Nov 2017, kan.liang@...el.com wrote:
> From: Kan Liang <Kan.liang@...el.com>
>
> Some uncore has custom pmu. For custom pmu, it does not need to
> customize everything. For example, it only needs to customize init()
> function for client IMC uncore. Other functions like
> add()/del()/start()/stop()/read() can use generic code.
>
> Expose the uncore_pmu_event_add/del/start/stop functions.
>
> Signed-off-by: Kan Liang <Kan.liang@...el.com>
Reviewed-by: Thomas Gleixner <tglx@...utronix.de>
Powered by blists - more mailing lists