[PATCH v6 0/2] perf: ARM CoreSight PMU support

[Will Deacon]

On Mon, Nov 07, 2022 at 05:11:07PM +0000, Besar Wicaksono wrote:
> Hi Will,
> 
> > -----Original Message-----
> > From: Will Deacon <will at kernel.org>
> > Sent: Monday, November 7, 2022 9:53 AM
> > To: Besar Wicaksono <bwicaksono at nvidia.com>
> > Cc: suzuki.poulose at arm.com; robin.murphy at arm.com;
> > catalin.marinas at arm.com; mark.rutland at arm.com; linux-arm-
> > kernel at lists.infradead.org; linux-kernel at vger.kernel.org; linux-
> > tegra at vger.kernel.org; sudeep.holla at arm.com;
> > thanu.rangarajan at arm.com; Michael.Williams at arm.com; Thierry Reding
> > <treding at nvidia.com>; Jonathan Hunter <jonathanh at nvidia.com>; Vikram
> > Sethi <vsethi at nvidia.com>; mathieu.poirier at linaro.org;
> > mike.leach at linaro.org; leo.yan at linaro.org
> > Subject: Re: [PATCH v6 0/2] perf: ARM CoreSight PMU support
> > 
> > External email: Use caution opening links or attachments
> > 
> > 
> > On Thu, Sep 29, 2022 at 09:34:41PM -0500, Besar Wicaksono wrote:
> > > Add driver support for ARM CoreSight PMU device and event attributes for
> > NVIDIA
> > > implementation. The code is based on ARM Coresight PMU architecture
> > and ACPI ARM
> > > Performance Monitoring Unit table (APMT) specification below:
> > >  * ARM Coresight PMU:
> > >         https://developer.arm.com/documentation/ihi0091/latest
> > >  * APMT: https://developer.arm.com/documentation/den0117/latest
> > >
> > > The patchset applies on top of
> > >   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> > >   master next-20220524
> > >
> > > For APMT support, please see patchset:
> > https://lkml.org/lkml/2022/4/19/1395
> > >
> > > Changes from v5:
> > >  * Default get_event/format_attrs callback now returns copy of default
> > array.
> > > Thanks to suzuki.poulose at arm.com for the review comments.
> > > v5: https://lore.kernel.org/linux-arm-kernel/20220928201830.45637-1-
> > bwicaksono at nvidia.com/
> > 
> > These patches no longer apply. Please can you rebase onto -rc4 and drop the
> > defconfig change from the first patch?
> 
> Why does the defconfig change need to be dropped ?

Oh, just because that file is a big source of conflicts so I'd prefer to
keep defconfig changes separate from patches which add new functionality.

Will