[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1573002091-9744-1-git-send-email-gkulkarni@marvell.com>
Date: Wed, 6 Nov 2019 01:01:39 +0000
From: Ganapatrao Prabhakerrao Kulkarni <gkulkarni@...vell.com>
To: "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
CC: "peterz@...radead.org" <peterz@...radead.org>,
"mingo@...hat.com" <mingo@...hat.com>,
"will@...nel.org" <will@...nel.org>,
"mark.rutland@....com" <mark.rutland@....com>,
"corbet@....net" <corbet@....net>,
"gklkml16@...il.com" <gklkml16@...il.com>
Subject: [PATCH 0/2] Workaround for ThunderX2 erratum 221
This erratum is found when system hang reported by internal
benchmarking team while they were trying ThunderX2 PMU uncore
events along with cpu/memory intensive applications like stream,
SPECjbb, SPECInt, etc.
The workaround is to disable event multiplexing.
The current Perf core does not provide any provision to PMUs
to disable event multiplexing. In first patch, adding PMU
capability to disable event multiplexing in perf core.
In second patch, setting the capability to disable for
the ThunderX2 UNCORE PMUs.
Ganapatrao Prabhakerrao Kulkarni (2):
perf/core: Adding capability to disable PMUs event multiplexing
Thunderx2, uncore: Add workaround for ThunderX2 erratum 221
Documentation/admin-guide/perf/thunderx2-pmu.rst | 9 +++++++++
drivers/perf/thunderx2_pmu.c | 3 ++-
include/linux/perf_event.h | 1 +
kernel/events/core.c | 8 ++++++++
4 files changed, 20 insertions(+), 1 deletion(-)
--
2.17.1
Powered by blists - more mailing lists