All of lore.kernel.org
 help / color / mirror / Atom feed
From: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
To: "H. Peter Anvin" <hpa@linux.intel.com>
Cc: Jingbai Ma <jingbai.ma@hp.com>,
	"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Borislav Petkov <bp@alien8.de>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Fengguang Wu <fengguang.wu@intel.com>,
	Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [PATCH v10] x86, apic, kexec, Documentation: Add disable_cpu_apic kernel parameter
Date: Tue, 14 Jan 2014 20:41:29 +0900	[thread overview]
Message-ID: <52D52269.6070705@jp.fujitsu.com> (raw)
In-Reply-To: <20131210144910.GC13909@redhat.com>

(2013/12/10 23:49), Vivek Goyal wrote:
> On Wed, Dec 04, 2013 at 05:10:58PM +0900, HATAYAMA Daisuke wrote:
>> This patch set is to allow kdump 2nd kernel to wake up multiple CPUs,
>> 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.
>>
>> At v4, 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_apicid kernel parameter,
>> which is newly introduced by 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.
>
> Hi hpa,
>
> Can you please consider this patch for inclusion.
>
> Thanks
> Vivek
>

Hello HPA,

Could you please give me a next feedback for inclusion?

This patch set has already been acked by Vivek and now I'm waiting for a reaction of x86 maintainers.

-- 
Thanks.
HATAYAMA, Daisuke


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
To: "H. Peter Anvin" <hpa@linux.intel.com>
Cc: Vivek Goyal <vgoyal@redhat.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Fengguang Wu <fengguang.wu@intel.com>,
	Borislav Petkov <bp@alien8.de>,
	"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jingbai Ma <jingbai.ma@hp.com>
Subject: Re: [PATCH v10] x86, apic, kexec, Documentation: Add disable_cpu_apic kernel parameter
Date: Tue, 14 Jan 2014 20:41:29 +0900	[thread overview]
Message-ID: <52D52269.6070705@jp.fujitsu.com> (raw)
In-Reply-To: <20131210144910.GC13909@redhat.com>

(2013/12/10 23:49), Vivek Goyal wrote:
> On Wed, Dec 04, 2013 at 05:10:58PM +0900, HATAYAMA Daisuke wrote:
>> This patch set is to allow kdump 2nd kernel to wake up multiple CPUs,
>> 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.
>>
>> At v4, 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_apicid kernel parameter,
>> which is newly introduced by 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.
>
> Hi hpa,
>
> Can you please consider this patch for inclusion.
>
> Thanks
> Vivek
>

Hello HPA,

Could you please give me a next feedback for inclusion?

This patch set has already been acked by Vivek and now I'm waiting for a reaction of x86 maintainers.

-- 
Thanks.
HATAYAMA, Daisuke


  parent reply	other threads:[~2014-01-14 11:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-04  8:10 [PATCH v10] x86, apic, kexec, Documentation: Add disable_cpu_apic kernel parameter HATAYAMA Daisuke
2013-12-04  8:10 ` HATAYAMA Daisuke
2013-12-04 21:06 ` Vivek Goyal
2013-12-04 21:06   ` Vivek Goyal
2013-12-10 14:49 ` Vivek Goyal
2013-12-10 14:49   ` Vivek Goyal
2013-12-13 21:08   ` jerry.hoemann
2013-12-13 21:08     ` jerry.hoemann
2014-01-14 11:41   ` HATAYAMA Daisuke [this message]
2014-01-14 11:41     ` 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=52D52269.6070705@jp.fujitsu.com \
    --to=d.hatayama@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --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.