From: Tony Luck <tony.luck@intel.com>
To: Orange Kao <orange@aiven.io>
Cc: qiuxu.zhuo@intel.com, bp@alien8.de, james.morse@arm.com,
orange@kaosy.org, linux-edac@vger.kernel.org,
linux-kernel@vger.kernel.org, mchehab@kernel.org,
rric@kernel.org
Subject: Re: [PATCH 0/3] EDAC/igen6: Add polling support and allow setting edac_op_state
Date: Fri, 8 Nov 2024 13:44:12 -0800 [thread overview]
Message-ID: <Zy6GLJwyZCuGwdni@agluck-desk3> (raw)
In-Reply-To: <20241106114024.941659-1-orange@aiven.io>
On Wed, Nov 06, 2024 at 11:35:44AM +0000, Orange Kao wrote:
> Thank you Qiuxu and Boris.
>
> Here is the updated patch. I would like to propose that we keep the
> edac_op_state as a module parameter. Because it would allow users (regardless of
> CPU SKU) to test different options on their machine without compiling their own
> kernel. I hope this could lower the entry barrier and make it easier for them to
> test IBECC.
>
> Patch 1: Initialize edac_op_state according to the configuration data
> Patch 2: Add polling support
Applied patches 1 & 2 to RAS tree. Thanks
> Patch 3: Allow setting edac_op_state
As discussed on mailing list, not taking this one as there
is no real use case.
-Tony
prev parent reply other threads:[~2024-11-08 21:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 11:35 [PATCH 0/3] EDAC/igen6: Add polling support and allow setting edac_op_state Orange Kao
2024-11-06 11:35 ` [PATCH 1/3] EDAC/igen6: Initialize edac_op_state according to the configuration data Orange Kao
2024-11-06 11:35 ` [PATCH 2/3] EDAC/igen6: Add polling support Orange Kao
2024-11-07 11:53 ` Zhuo, Qiuxu
2024-11-06 11:35 ` [PATCH 3/3] EDAC/igen6: Allow setting edac_op_state Orange Kao
2024-11-06 13:04 ` Zhuo, Qiuxu
2024-11-06 21:23 ` Orange Kao
2024-11-06 12:05 ` [PATCH 0/3] EDAC/igen6: Add polling support and allow " Borislav Petkov
2024-11-08 21:44 ` Tony Luck [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zy6GLJwyZCuGwdni@agluck-desk3 \
--to=tony.luck@intel.com \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=orange@aiven.io \
--cc=orange@kaosy.org \
--cc=qiuxu.zhuo@intel.com \
--cc=rric@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox