[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SJ1PR11MB6083BB314BDEDB397861C845FC96A@SJ1PR11MB6083.namprd11.prod.outlook.com>
Date: Tue, 13 May 2025 22:07:13 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Yazen Ghannam <yazen.ghannam@....com>, Borislav Petkov <bp@...en8.de>
CC: "x86@...nel.org" <x86@...nel.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "linux-edac@...r.kernel.org"
<linux-edac@...r.kernel.org>, "Smita.KoralahalliChannabasappa@....com"
<Smita.KoralahalliChannabasappa@....com>, "Zhuo, Qiuxu"
<qiuxu.zhuo@...el.com>
Subject: RE: [PATCH v3 17/17] x86/mce: Restore poll settings after storm
subsides
> On AMD, polling and interrupt are independent. We still poll all banks
> even if they are interrupt-capable. I think we discussed this in a
> previous revision of this set.
Can you race and double report the same error if a polling interval
and interrupt happen together?
Disabling polling for interrupt capable banks happened before I
started looking at this code. But I assumed it was to avoid double
report.
-Tony
Powered by blists - more mailing lists