All of lore.kernel.org
 help / color / mirror / Atom feed
From: jerry.hoemann@hp.com
To: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
Cc: hpa@linux.intel.com, ebiederm@xmission.com, vgoyal@redhat.com,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	bp@alien8.de, akpm@linux-foundation.org, fengguang.wu@intel.com,
	jingbai.ma@hp.com
Subject: Re: [PATCH v4 0/3] x86, apic, kexec: Add disable_cpu_apic kernel parameter
Date: Tue, 22 Oct 2013 16:08:03 -0600	[thread overview]
Message-ID: <20131022220803.GA32387@anatevka.fc.hp.com> (raw)
In-Reply-To: <20131022150015.24240.39686.stgit@localhost6.localdomain6>

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

> 
> v2 => v3)
> 
> - Change default value of boot_cpu_is_bsp to true.
> 
> - Before executing rdmsr(MSR_IA32_APICBASE), check if the number of
>   processor family is larger than or equal to 6 in order to avoid
>   invalid opcode exception on processors where MSR_IA32_APICBASE is
>   not supported.
> 
> v1 => v2)
> 
> - Rebased on top of v3.12-rc5.
> 
> - Fix linking time error of boot_cpu_is_bsp_init() in case of
>   CONFIG_LOCAL_APIC disabled by adding empty static inline function
>   instead.
> 
> - Fix missing feature check by means of cpu_has_apic macro in
>   boot_cpu_is_bsp_init() before calling rdmsr_safe(MSR_IA32_APICBASE).
> 
>   NOTE: I've checked local apic-present case only; I don't have any
>   x86 processor without local apic.
> 
> - Add __init annotation to boot_cpu_is_bsp_init().
> 
> Test
> 
> - built with and without CONFIG_LOCAL_APIC
> - tested x86_64 in case of acpi and MP table
> 
> ---
> 
> HATAYAMA Daisuke (3):
>       x86, apic: Don't count the CPU with BP flag from MP table as booting-up CPU
>       x86, apic: Add disable_cpu_apicid kernel parameter
>       Documentation, x86, apic, kexec: Add disable_cpu_apicid kernel parameter
> 
> 
>  Documentation/kernel-parameters.txt |    9 +++++++++
>  arch/x86/kernel/apic/apic.c         |   29 +++++++++++++++++++++++++++++
>  arch/x86/kernel/mpparse.c           |    1 -
>  3 files changed, 38 insertions(+), 1 deletion(-)
> 
> -- 
> 
> Thanks.
> HATAYAMA, Daisuke
> 
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec

-- 

----------------------------------------------------------------------------
Jerry Hoemann            Software Engineer              Hewlett-Packard/MODL

3404 E Harmony Rd. MS 57                        phone:  (970) 898-1022
Ft. Collins, CO 80528                           FAX:    (970) 898-XXXX
                                                email:  jerry.hoemann@hp.com
----------------------------------------------------------------------------


  parent reply	other threads:[~2013-10-22 22:08 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-22 15:01 [PATCH v4 0/3] x86, apic, kexec: Add disable_cpu_apic kernel parameter HATAYAMA Daisuke
2013-10-22 15:01 ` HATAYAMA Daisuke
2013-10-22 15:01 ` [PATCH v4 1/3] x86, apic: Don't count the CPU with BP flag from MP table as booting-up CPU HATAYAMA Daisuke
2013-10-22 15:01   ` HATAYAMA Daisuke
2013-11-08 16:08   ` Vivek Goyal
2013-11-08 16:08     ` Vivek Goyal
2013-11-11  2:52     ` HATAYAMA Daisuke
2013-11-11  2:52       ` HATAYAMA Daisuke
2013-11-11 16:52       ` Vivek Goyal
2013-11-11 16:52         ` Vivek Goyal
2013-11-12  0:40         ` HATAYAMA Daisuke
2013-11-12  0:40           ` HATAYAMA Daisuke
2013-11-12  9:58           ` HATAYAMA Daisuke
2013-11-12  9:58             ` HATAYAMA Daisuke
2013-10-22 15:01 ` [PATCH v4 2/3] x86, apic: Add disable_cpu_apicid kernel parameter HATAYAMA Daisuke
2013-10-22 15:01   ` HATAYAMA Daisuke
2013-10-22 15:01 ` [PATCH v4 3/3] Documentation, x86, apic, kexec: " HATAYAMA Daisuke
2013-10-22 15:01   ` HATAYAMA Daisuke
2013-10-22 22:08 ` jerry.hoemann [this message]
2013-10-23  0:05   ` [PATCH v4 0/3] x86, apic, kexec: Add disable_cpu_apic " HATAYAMA Daisuke
2013-10-23  0:05     ` HATAYAMA Daisuke
2013-10-23 15:51     ` Vivek Goyal
2013-10-23 15:51       ` Vivek Goyal
2013-10-24  1:42       ` HATAYAMA Daisuke
2013-10-24  1:42         ` HATAYAMA Daisuke
2013-10-25 11:05         ` Petr Tesarik
2013-10-29  0:53           ` HATAYAMA Daisuke
2013-10-29  7:39             ` Petr Tesarik
2013-10-24  5:50       ` Eric W. Biederman
2013-10-24  5:50         ` Eric W. Biederman
2013-10-31  0:58     ` jerry.hoemann
2013-10-31  4:43       ` HATAYAMA Daisuke
2013-10-31  4:43         ` HATAYAMA Daisuke
2013-10-31 13:27       ` Vivek Goyal
2013-10-31 13:27         ` Vivek Goyal
2013-11-01  0:31         ` Simon Horman
2013-11-01  0:31           ` Simon Horman
2013-11-01  7:54         ` jerry.hoemann
2013-11-04  7:08         ` HATAYAMA Daisuke
2013-11-04  7:08           ` HATAYAMA Daisuke
2013-10-29 14:21 ` Baoquan He
2013-10-29 14:21   ` Baoquan He
2013-10-30  0:44   ` HATAYAMA Daisuke
2013-10-30  0:44     ` HATAYAMA Daisuke
2013-10-30  6:06     ` Baoquan He
2013-10-30  6:06       ` Baoquan He
2013-10-30  9:48       ` HATAYAMA Daisuke
2013-10-30  9:48         ` HATAYAMA Daisuke
2013-10-30 15:27   ` Baoquan He
2013-10-30 15:27     ` Baoquan He
2013-11-06 19:02 ` jerry.hoemann
2013-11-11  4:49   ` HATAYAMA Daisuke
2013-11-11  4:49     ` HATAYAMA Daisuke
2013-11-13 18:27     ` jerry.hoemann
2013-11-08  3:30 ` Baoquan He
2013-11-08  3:30   ` Baoquan He
2013-11-08  4:13   ` HATAYAMA Daisuke
2013-11-08  4:13     ` HATAYAMA Daisuke

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=20131022220803.GA32387@anatevka.fc.hp.com \
    --to=jerry.hoemann@hp.com \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=d.hatayama@jp.fujitsu.com \
    --cc=ebiederm@xmission.com \
    --cc=fengguang.wu@intel.com \
    --cc=hpa@linux.intel.com \
    --cc=jingbai.ma@hp.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.