On Monday, August 8, 2022 2:57 PM, Borislav Petkov wrote: > On Mon, Aug 08, 2022 at 08:40:18PM +0000, Kani, Toshi wrote: > > This allows ghes_edac_register() to run before edac_init(), and sets > > edac_mc_owner to prevent chipset-specific edac driver > > So this is the important part: how does it get decided which EDAC driver > to load? The chipset-specific one or the FW glue one? > > User, policy, etc? Whichever loaded first wins. Chipset-specific one checks with chipset IDs but does not check with GHES. Hence, ghes_edac_register() needs to run before chipset-specific one. Toshi
