From: Ganapatrao Prabhakerrao Kulkarni <gkulkarni@marvell.com>
To: "linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Cc: "peterz@infradead.org" <peterz@infradead.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"will@kernel.org" <will@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"gklkml16@gmail.com" <gklkml16@gmail.com>
Subject: [PATCH 0/2] Workaround for ThunderX2 erratum 221
Date: Wed, 6 Nov 2019 01:01:39 +0000 [thread overview]
Message-ID: <1573002091-9744-1-git-send-email-gkulkarni@marvell.com> (raw)
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
WARNING: multiple messages have this Message-ID (diff)
From: Ganapatrao Prabhakerrao Kulkarni <gkulkarni@marvell.com>
To: "linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"peterz@infradead.org" <peterz@infradead.org>,
"gklkml16@gmail.com" <gklkml16@gmail.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"will@kernel.org" <will@kernel.org>
Subject: [PATCH 0/2] Workaround for ThunderX2 erratum 221
Date: Wed, 6 Nov 2019 01:01:39 +0000 [thread overview]
Message-ID: <1573002091-9744-1-git-send-email-gkulkarni@marvell.com> (raw)
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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-11-06 1:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 1:01 Ganapatrao Prabhakerrao Kulkarni [this message]
2019-11-06 1:01 ` [PATCH 0/2] Workaround for ThunderX2 erratum 221 Ganapatrao Prabhakerrao Kulkarni
2019-11-06 1:01 ` [PATCH 1/2] perf/core: Adding capability to disable PMUs event multiplexing Ganapatrao Prabhakerrao Kulkarni
2019-11-06 1:01 ` Ganapatrao Prabhakerrao Kulkarni
2019-11-06 9:40 ` Peter Zijlstra
2019-11-06 9:40 ` Peter Zijlstra
2019-11-06 9:58 ` Peter Zijlstra
2019-11-06 9:58 ` Peter Zijlstra
2019-11-06 11:28 ` Mark Rutland
2019-11-06 11:28 ` Mark Rutland
2019-11-06 23:28 ` Ganapatrao Kulkarni
2019-11-06 23:28 ` Ganapatrao Kulkarni
2019-11-07 14:35 ` Ganapatrao Kulkarni
2019-11-07 14:35 ` Ganapatrao Kulkarni
2019-11-07 14:52 ` Mark Rutland
2019-11-07 14:52 ` Mark Rutland
2019-11-07 15:45 ` Ganapatrao Kulkarni
2019-11-07 15:45 ` Ganapatrao Kulkarni
2019-11-07 15:54 ` Mark Rutland
2019-11-07 15:54 ` Mark Rutland
2019-11-07 15:04 ` Peter Zijlstra
2019-11-07 15:04 ` Peter Zijlstra
2019-11-07 23:17 ` kbuild test robot
2019-11-07 23:17 ` kbuild test robot
2019-11-07 23:17 ` kbuild test robot
2019-11-06 1:01 ` [PATCH 2/2] Thunderx2, uncore: Add workaround for ThunderX2 erratum 221 Ganapatrao Prabhakerrao Kulkarni
2019-11-06 1:01 ` Ganapatrao Prabhakerrao Kulkarni
2019-11-06 11:37 ` Mark Rutland
2019-11-06 11:37 ` Mark Rutland
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=1573002091-9744-1-git-send-email-gkulkarni@marvell.com \
--to=gkulkarni@marvell.com \
--cc=corbet@lwn.net \
--cc=gklkml16@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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: link
Be 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.