From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Xiaofei Tan <tanxiaofei@huawei.com>
Cc: <rafael@kernel.org>, <lenb@kernel.org>,
<linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<mchehab+huawei@kernel.org>, <roberto.sassu@huawei.com>,
<shiju.jose@huawei.com>, <prime.zeng@hisilicon.com>,
<linuxarm@huawei.com>
Subject: Re: [PATCH v3] acpi: Fix HED module initialization order when it is built-in
Date: Mon, 20 Jan 2025 11:04:17 +0000 [thread overview]
Message-ID: <20250120110417.00000a57@huawei.com> (raw)
In-Reply-To: <20250117022957.25227-1-tanxiaofei@huawei.com>
On Fri, 17 Jan 2025 10:29:57 +0800
Xiaofei Tan <tanxiaofei@huawei.com> wrote:
> When the module HED is built-in, the module HED init is behind EVGED
> as the driver are in the same initcall level, then the order is determined
> by Makefile order. That order violates expectations. Because RAS records
> can't be handled in the special time window that EVGED has initialized
> while HED not.
>
> If the number of such RAS records is more than the APEI HEST error source
> number, the HEST resources could be occupied all, and then could affect
> subsequent RAS error reporting.
>
> Change the initcall level of HED to subsys_init to fix the issue. If build
> HED as a module, the problem remains. To solve this problem completely,
> change the ACPI_HED from tristate to bool.
>
> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Given the change in approach (even though I reviewed this internally)
should probably have dropped my RB. Anyhow, consider this me
giving it again on list.
Thanks,
Jonathan
> Signed-off-by: Xiaofei Tan <tanxiaofei@huawei.com>
> ---
> drivers/acpi/Kconfig | 2 +-
> drivers/acpi/hed.c | 1 +
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig
> index d81b55f5068c..7f10aa38269d 100644
> --- a/drivers/acpi/Kconfig
> +++ b/drivers/acpi/Kconfig
> @@ -452,7 +452,7 @@ config ACPI_SBS
> the modules will be called sbs and sbshc.
>
> config ACPI_HED
> - tristate "Hardware Error Device"
> + bool "Hardware Error Device"
> help
> This driver supports the Hardware Error Device (PNP0C33),
> which is used to report some hardware errors notified via
> diff --git a/drivers/acpi/hed.c b/drivers/acpi/hed.c
> index 7652515a6be1..677dfcce2990 100644
> --- a/drivers/acpi/hed.c
> +++ b/drivers/acpi/hed.c
> @@ -81,6 +81,7 @@ static struct acpi_driver acpi_hed_driver = {
> },
> };
> module_acpi_driver(acpi_hed_driver);
> +subsys_initcall(acpi_hed_driver_init);
>
> MODULE_AUTHOR("Huang Ying");
> MODULE_DESCRIPTION("ACPI Hardware Error Device Driver");
next prev parent reply other threads:[~2025-01-20 11:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 2:29 [PATCH v3] acpi: Fix HED module initialization order when it is built-in Xiaofei Tan
2025-01-20 11:04 ` Jonathan Cameron [this message]
2025-01-21 2:23 ` Xiaofei Tan
2025-01-23 19:35 ` Rafael J. Wysocki
2025-01-29 4:33 ` Nathan Chancellor
2025-01-29 9:44 ` Rafael J. Wysocki
2025-02-06 2:44 ` Xiaofei Tan
2025-02-06 16:49 ` Nathan Chancellor
2025-02-07 8:22 ` Xiaofei Tan
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=20250120110417.00000a57@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mchehab+huawei@kernel.org \
--cc=prime.zeng@hisilicon.com \
--cc=rafael@kernel.org \
--cc=roberto.sassu@huawei.com \
--cc=shiju.jose@huawei.com \
--cc=tanxiaofei@huawei.com \
/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