RE: [PATCH v2 5/7] EDAC/ghes: Prevent chipset-specific edac from loading after ghes_edac is registered

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Borislav Petkov <bp@xxxxxxxxx>
Subject: RE: [PATCH v2 5/7] EDAC/ghes: Prevent chipset-specific edac from loading after ghes_edac is registered
From: "Kani, Toshi" <toshi.kani@xxxxxxx>
Date: Fri, 19 Aug 2022 18:53:41 +0000
Accept-language: en-US
Cc: Justin He <Justin.He@xxxxxxx>, "linux-acpi@xxxxxxxxxxxxxxx" <linux-acpi@xxxxxxxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, "linux-edac@xxxxxxxxxxxxxxx" <linux-edac@xxxxxxxxxxxxxxx>, "devel@xxxxxxxxxx" <devel@xxxxxxxxxx>, "Rafael J . Wysocki" <rafael@xxxxxxxxxx>, Shuai Xue <xueshuai@xxxxxxxxxxxxxxxxx>, Jarkko Sakkinen <jarkko@xxxxxxxxxx>, "linux-efi@xxxxxxxxxxxxxxx" <linux-efi@xxxxxxxxxxxxxxx>, nd <nd@xxxxxxx>, Ard Biesheuvel <ardb@xxxxxxxxxx>, Len Brown <lenb@xxxxxxxxxx>, James Morse <James.Morse@xxxxxxx>, Tony Luck <tony.luck@xxxxxxxxx>, Mauro Carvalho Chehab <mchehab@xxxxxxxxxx>, Robert Richter <rric@xxxxxxxxxx>, Robert Moore <robert.moore@xxxxxxxxx>, Qiuxu Zhuo <qiuxu.zhuo@xxxxxxxxx>, Yazen Ghannam <yazen.ghannam@xxxxxxx>
In-reply-to: <Yv/batVmSf7PDRcL@zn.tnic>
References: <20220817143458.335938-1-justin.he@arm.com> <20220817143458.335938-6-justin.he@arm.com> <DM4PR84MB18538A56870A280CDC4637A7826C9@DM4PR84MB1853.NAMPRD84.PROD.OUTLOOK.COM> <DBBPR08MB453891E87563F1BBE291248AF76C9@DBBPR08MB4538.eurprd08.prod.outlook.com> <DM4PR84MB1853B213F2F45E495D9D6446826C9@DM4PR84MB1853.NAMPRD84.PROD.OUTLOOK.COM> <Yv/Wm/Zf0kdGgT33@zn.tnic> <DM4PR84MB185306C2C0DE95FF408173BA826C9@DM4PR84MB1853.NAMPRD84.PROD.OUTLOOK.COM> <Yv/batVmSf7PDRcL@zn.tnic>
Thread-index: AQHYskazgdaGLeNebEWQzyv29780RK21ZjbQgACj04CAAE7iUIAANdmAgAADCCCAAAKzAIAAAGBA
Thread-topic: [PATCH v2 5/7] EDAC/ghes: Prevent chipset-specific edac from loading after ghes_edac is registered

On Friday, August 19, 2022 12:50 PM, Borislav Petkov wrote:
> > 3. ghes_probe() is not called,
> 
> When is ghes_probe() not called on ARM?

When the system does not implement ACPI GHES table,
which I suppose is most of the case on ARM.

Toshi

Follow-Ups:
- Re: [PATCH v2 5/7] EDAC/ghes: Prevent chipset-specific edac from loading after ghes_edac is registered
  - From: Borislav Petkov

References:
- [PATCH v2 0/7] Modularize ghes_edac driver
  - From: Jia He
- [PATCH v2 5/7] EDAC/ghes: Prevent chipset-specific edac from loading after ghes_edac is registered
  - From: Jia He
- RE: [PATCH v2 5/7] EDAC/ghes: Prevent chipset-specific edac from loading after ghes_edac is registered
  - From: Kani, Toshi
- RE: [PATCH v2 5/7] EDAC/ghes: Prevent chipset-specific edac from loading after ghes_edac is registered
  - From: Justin He
- RE: [PATCH v2 5/7] EDAC/ghes: Prevent chipset-specific edac from loading after ghes_edac is registered
  - From: Kani, Toshi
- Re: [PATCH v2 5/7] EDAC/ghes: Prevent chipset-specific edac from loading after ghes_edac is registered
  - From: Borislav Petkov
- RE: [PATCH v2 5/7] EDAC/ghes: Prevent chipset-specific edac from loading after ghes_edac is registered
  - From: Kani, Toshi
- Re: [PATCH v2 5/7] EDAC/ghes: Prevent chipset-specific edac from loading after ghes_edac is registered
  - From: Borislav Petkov

Prev by Date: Re: [PATCH v2 5/7] EDAC/ghes: Prevent chipset-specific edac from loading after ghes_edac is registered
Next by Date: RE: [PATCH v2 5/7] EDAC/ghes: Prevent chipset-specific edac from loading after ghes_edac is registered
Previous by thread: Re: [PATCH v2 5/7] EDAC/ghes: Prevent chipset-specific edac from loading after ghes_edac is registered
Next by thread: Re: [PATCH v2 5/7] EDAC/ghes: Prevent chipset-specific edac from loading after ghes_edac is registered
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Security] [Bugtraq] [Linux OMAP] [Linux MIPS] [ECOS] [Asterisk Internet PBX] [Linux API]