[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5fa3e397-376b-42c1-9dbe-891e9916987c@zhaoxin.com>
Date: Fri, 20 Sep 2024 18:42:15 +0800
From: Tony W Wang-oc <TonyWWang-oc@...oxin.com>
To: Yazen Ghannam <yazen.ghannam@....com>
CC: <tglx@...utronix.de>, <mingo@...hat.com>, <bp@...en8.de>,
<dave.hansen@...ux.intel.com>, <x86@...nel.org>, <hpa@...or.com>,
<tony.luck@...el.com>, <linux-kernel@...r.kernel.org>,
<linux-edac@...r.kernel.org>, <CobeChen@...oxin.com>, <TimGuo@...oxin.com>,
<LeoLiu-oc@...oxin.com>, Lyle Li <LyleLi@...oxin.com>
Subject: Re: [PATCH v3 3/3] x86/mce: Add CMCI storm switching support for
Zhaoxin
On 2024/9/19 22:06, Yazen Ghannam wrote:
>
>> +void mce_zhaoxin_handle_storm(int bank, bool on)
>> +{
>> + unsigned long flags;
>> + u64 val;
>> +
>> + raw_spin_lock_irqsave(&cmci_discover_lock, flags);
>> + rdmsrl(MSR_IA32_MCx_CTL2(bank), val);
>> + if (on) {
>> + val &= ~(MCI_CTL2_CMCI_EN | MCI_CTL2_CMCI_THRESHOLD_MASK);
>> + val |= CMCI_STORM_THRESHOLD;
>> + } else {
>> + val &= ~MCI_CTL2_CMCI_THRESHOLD_MASK;
>> + val |= (MCI_CTL2_CMCI_EN | cmci_threshold[bank]);
>> + }
>> + wrmsrl(MSR_IA32_MCx_CTL2(bank), val);
>> + raw_spin_unlock_irqrestore(&cmci_discover_lock, flags);
>> +}
>
> Why does this need to be different than mce_intel_handle_storm()?
>
The reason is actually mentioned in the cover letter: "because Zhaoxin's
UCR error is not reported through CMCI", and we want to disable CMCI
interrupt when CMCI storm happened.
Sincerely
TonyWWang-oc
Powered by blists - more mailing lists