[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ada0da4e-4260-47c0-897f-09e3e1e1658e@amd.com>
Date: Wed, 13 Sep 2023 21:48:43 +0530
From: Sandipan Das <sandipan.das@....com>
To: Jirka Hladky <jhladky@...hat.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
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>, 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>,
Michael Petlan <mpetlan@...hat.com>
Subject: Re: [PATCH] perf/x86/amd: Do not WARN on every IRQ
Hi Jirka,
Can you please share the following?
1. Family, Model and Stepping of the processor
2. Microcode patch level
On 9/13/2023 8:00 PM, Jirka Hladky wrote:
> Hi Sandipan,
>
> Is there any update on this issue? We have hit the issue, and it makes
> the server pretty unusable due to the thousands of Call Traces being
> logged.
>
> Thanks a lot!
> Jirka
>
>
> On Fri, Jun 16, 2023 at 5:34 PM Peter Zijlstra <peterz@...radead.org> wrote:
>>
>> 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