[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230616153221.GI4253@hirez.programming.kicks-ass.net>
Date: Fri, 16 Jun 2023 17:32:21 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: "Sandipan Das (AMD)" <sandipandas1990@...il.com>
Cc: Breno Leitao <leitao@...ian.org>, Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>,
Namhyung Kim <namhyung@...nel.org>,
Ian Rogers <irogers@...gle.com>,
Adrian Hunter <adrian.hunter@...el.com>,
Thomas Gleixner <tglx@...utronix.de>,
Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
"H. Peter Anvin" <hpa@...or.com>,
Sandipan Das <sandipan.das@....com>, leit@...com,
dcostantino@...a.com,
"open list:PERFORMANCE EVENTS SUBSYSTEM"
<linux-perf-users@...r.kernel.org>,
"open list:PERFORMANCE EVENTS SUBSYSTEM"
<linux-kernel@...r.kernel.org>, ananth.narayan@....com,
Ravi Bangoria <ravi.bangoria@....com>
Subject: Re: [PATCH] perf/x86/amd: Do not WARN on every IRQ
On Fri, Jun 16, 2023 at 08:13:22PM +0530, Sandipan Das (AMD) wrote:
> The reserved bits should never be set. The purpose of the WARN_ON() is to catch such anomalies.
> I am working out the details with Breno and will report back with a resolution.
Thanks!
Powered by blists - more mailing lists