From: Bhaskara Budiredla <bbudiredla@marvell.com> To: Bharat Bhushan <bbhushan2@marvell.com>, "will@kernel.org" <will@kernel.org>, "mark.rutland@arm.com" <mark.rutland@arm.com>, "robh+dt@kernel.org" <robh+dt@kernel.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org> Subject: RE: [PATCH v4 2/4] perf/marvell: CN10k DDR performance monitor support Date: Tue, 12 Oct 2021 09:16:13 +0000 [thread overview] Message-ID: <CY4PR1801MB2070C952470F81D26C1BB43ADEB69@CY4PR1801MB2070.namprd18.prod.outlook.com> (raw) In-Reply-To: <CO6PR18MB4465FC607A2836EE98807965E3B69@CO6PR18MB4465.namprd18.prod.outlook.com> [...] >> >> v2->v3: >> - Add COMPILE_TEST as a dependency This is missing. >> - Switch to sysfs_emit() >> - Error propagation when invalif event requested >> - Switch to devm_platform_get_and_ioremap_resource() >> - Other review comments on v2. >> >> v1->v2: >> - writeq/readq changed to respective relaxed version >> - Using PMU_EVENT_ATTR_ID >> >> drivers/perf/Kconfig | 7 + >> drivers/perf/Makefile | 1 + >> drivers/perf/marvell_cn10k_ddr_pmu.c | 599 >> +++++++++++++++++++++++++++ >> 3 files changed, 607 insertions(+) >> create mode 100644 drivers/perf/marvell_cn10k_ddr_pmu.c >> >> diff --git a/drivers/perf/Kconfig b/drivers/perf/Kconfig index >> 77522e5efe11..41a80a4b8d29 100644 >> --- a/drivers/perf/Kconfig >> +++ b/drivers/perf/Kconfig >> @@ -139,4 +139,11 @@ config ARM_DMC620_PMU >> >> source "drivers/perf/hisilicon/Kconfig" >> >> +config MARVELL_CN10K_DDR_PMU >> + tristate "Enable MARVELL CN10K DRAM Subsystem(DSS) PMU >Support" >> + depends on ARM64 >> + help >> + Enable perf support for Marvell DDR Performance monitoring >> + event on CN10K platform. >> + >> endmenu
WARNING: multiple messages have this Message-ID (diff)
From: Bhaskara Budiredla <bbudiredla@marvell.com> To: Bharat Bhushan <bbhushan2@marvell.com>, "will@kernel.org" <will@kernel.org>, "mark.rutland@arm.com" <mark.rutland@arm.com>, "robh+dt@kernel.org" <robh+dt@kernel.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org> Subject: RE: [PATCH v4 2/4] perf/marvell: CN10k DDR performance monitor support Date: Tue, 12 Oct 2021 09:16:13 +0000 [thread overview] Message-ID: <CY4PR1801MB2070C952470F81D26C1BB43ADEB69@CY4PR1801MB2070.namprd18.prod.outlook.com> (raw) In-Reply-To: <CO6PR18MB4465FC607A2836EE98807965E3B69@CO6PR18MB4465.namprd18.prod.outlook.com> [...] >> >> v2->v3: >> - Add COMPILE_TEST as a dependency This is missing. >> - Switch to sysfs_emit() >> - Error propagation when invalif event requested >> - Switch to devm_platform_get_and_ioremap_resource() >> - Other review comments on v2. >> >> v1->v2: >> - writeq/readq changed to respective relaxed version >> - Using PMU_EVENT_ATTR_ID >> >> drivers/perf/Kconfig | 7 + >> drivers/perf/Makefile | 1 + >> drivers/perf/marvell_cn10k_ddr_pmu.c | 599 >> +++++++++++++++++++++++++++ >> 3 files changed, 607 insertions(+) >> create mode 100644 drivers/perf/marvell_cn10k_ddr_pmu.c >> >> diff --git a/drivers/perf/Kconfig b/drivers/perf/Kconfig index >> 77522e5efe11..41a80a4b8d29 100644 >> --- a/drivers/perf/Kconfig >> +++ b/drivers/perf/Kconfig >> @@ -139,4 +139,11 @@ config ARM_DMC620_PMU >> >> source "drivers/perf/hisilicon/Kconfig" >> >> +config MARVELL_CN10K_DDR_PMU >> + tristate "Enable MARVELL CN10K DRAM Subsystem(DSS) PMU >Support" >> + depends on ARM64 >> + help >> + Enable perf support for Marvell DDR Performance monitoring >> + event on CN10K platform. >> + >> endmenu _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-10-12 9:16 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-20 5:08 [PATCH v4 0/4] cn10k DDR Performance monitor support Bharat Bhushan 2021-09-20 5:08 ` Bharat Bhushan 2021-09-20 5:08 ` [PATCH v4 1/4] dt-bindings: perf: marvell: cn10k ddr performance monitor Bharat Bhushan 2021-09-20 5:08 ` Bharat Bhushan 2021-10-12 8:01 ` Bharat Bhushan 2021-10-12 8:01 ` Bharat Bhushan 2021-09-20 5:08 ` [PATCH v4 2/4] perf/marvell: CN10k DDR performance monitor support Bharat Bhushan 2021-09-20 5:08 ` Bharat Bhushan 2021-10-12 8:01 ` Bharat Bhushan 2021-10-12 8:01 ` Bharat Bhushan 2021-10-12 9:16 ` Bhaskara Budiredla [this message] 2021-10-12 9:16 ` Bhaskara Budiredla 2021-09-20 5:08 ` [PATCH v4 3/4] perf/marvell: cn10k DDR perfmon event overflow handling Bharat Bhushan 2021-09-20 5:08 ` Bharat Bhushan 2021-10-12 8:01 ` Bharat Bhushan 2021-10-12 8:01 ` Bharat Bhushan 2021-09-20 5:08 ` [PATCH v4 4/4] perf/marvell: cn10k DDR perf event core ownership Bharat Bhushan 2021-09-20 5:08 ` Bharat Bhushan 2021-10-12 8:02 ` Bharat Bhushan 2021-10-12 8:02 ` Bharat Bhushan 2021-09-29 9:04 ` [PATCH v4 0/4] cn10k DDR Performance monitor support Bharat Bhushan 2021-09-29 9:04 ` Bharat Bhushan 2021-10-12 8:01 ` Bharat Bhushan 2021-10-12 8:01 ` Bharat Bhushan
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=CY4PR1801MB2070C952470F81D26C1BB43ADEB69@CY4PR1801MB2070.namprd18.prod.outlook.com \ --to=bbudiredla@marvell.com \ --cc=bbhushan2@marvell.com \ --cc=devicetree@vger.kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mark.rutland@arm.com \ --cc=robh+dt@kernel.org \ --cc=will@kernel.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.