(2013/10/23 7:08), jerry.hoemann at hp.com wrote: > On Wed, Oct 23, 2013 at 12:01:18AM +0900, HATAYAMA Daisuke wrote: >> This patch set is to allow kdump 2nd kernel to wake up multiple CPUs >> even if 1st kernel crashs on some AP, a continueing work from: >> >> [PATCH v3 0/2] x86, apic, kdump: Disable BSP if boot cpu is AP >> https://lkml.org/lkml/2013/10/16/300. >> >> In this version, basic design has changed. Now users need to figure >> out initial APIC ID of BSP in the 1st kernel and configures kernel >> parameter for the 2nd kernel manually using disable_cpu_apic kernel >> parameter to be newly introduced in this patch set. This design is >> more flexible than the previous version in that we no longer have to >> rely on ACPI/MP table to get initial APIC ID of BSP. >> >> Sorry, this patch set have not include in-source documentation >> requested by Borislav Petkov yet, but I'll post it later separately, >> which would be better to focus on documentation reviewing. >> >> ChangeLog >> >> v3 => v4) >> >> - Rebased on top of v3.12-rc6 >> >> - Basic design has been changed. Now users need to figure out initial >> APIC ID of BSP in the 1st kernel and configures kernel parameter for >> the 2nd kernel manually using disable_cpu_apic kernel parameter to >> be newly introduced in this patch set. This design is more flexible >> than the previous version in that we no longer have to rely on >> ACPI/MP table to get initial APIC ID of BSP. > > > Do you literally mean a human at each boot will have to configure > the kdump configuration files for passing disable_cpu_apic? > Or do you envision the setting of disable_cpu_apic being put into > the kdump initialization scripts? > > thanks > > Jerry Nearer to the former case, but this is not what a human should do. It's a cumbersome task. I think, on fedora/RHEL system for example, kdump service should check at each boot automatically. -- Thanks. HATAYAMA, Daisuke
