[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CY8PR11MB7134C2A2328E5B8B3285C81489532@CY8PR11MB7134.namprd11.prod.outlook.com>
Date: Wed, 6 Nov 2024 13:04:41 +0000
From: "Zhuo, Qiuxu" <qiuxu.zhuo@...el.com>
To: Orange Kao <orange@...en.io>, "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
> 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
Powered by blists - more mailing lists