linux-kernel - Re: [PATCH 3/3] EDAC/igen6: Allow setting edac_op

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <9c7b9fad-408d-4767-9aeb-4e2333b0ece9@aiven.io>
Date: Wed, 6 Nov 2024 21:23:07 +0000
From: Orange Kao <orange@...en.io>
To: "Zhuo, Qiuxu" <qiuxu.zhuo@...el.com>, "Luck, Tony" <tony.luck@...el.com>
Cc: "bp@...en8.de" <bp@...en8.de>, "james.morse@....com"
 <james.morse@....com>, "orange@...sy.org" <orange@...sy.org>,
 "linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
 "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
 "mchehab@...nel.org" <mchehab@...nel.org>, "rric@...nel.org"
 <rric@...nel.org>
Subject: Re: [PATCH 3/3] EDAC/igen6: Allow setting edac_op_state

On 6/11/24 13:04, Zhuo, Qiuxu wrote:
>> From: Orange Kao <orange@...en.io>
>> [...]
>> Subject: [PATCH 3/3] EDAC/igen6: Allow setting edac_op_state
>>
>> Current implementation does not allow users to set edac_op_state. As a
>> result, if a user needs to test different edac_op_state, they need to compile
>> the kernel.
>>
>> This commit accepts module parameter edac_op_state which makes it easier
>> for users to test IBECC on their hardware.
> 
> An SoC's (with the IBECC feature) memory error reporting type is determined.
> Switching from NMI to Machine Check or vice versa for a given SoC is pointless
> in the real world.
> 
> Additionally, the interrupt mode is preferred over the polling mode unless
> the interrupt cannot work, as in the case you reported.
> 
> [ Sometimes, no choice is the best choice :-). ]
> 
> -Qiuxu

Thank you Qiuxu and Boris. Good to know. I don't have any "actual" use 
case so please exclude patch 3.

Thanks