From: "H. Peter Anvin" <hpa@linux.intel.com>
To: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
Cc: ebiederm@xmission.com, vgoyal@redhat.com,
akpm@linux-foundation.org, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, jingbai.ma@hp.com
Subject: Re: [PATCH 0/2] x86, apic: Disable BSP if boot cpu is AP
Date: Thu, 29 Aug 2013 06:54:31 -0700 [thread overview]
Message-ID: <521F5297.4070906@linux.intel.com> (raw)
In-Reply-To: <20130829092458.5476.10277.stgit@localhost6.localdomain6>
On 08/29/2013 02:27 AM, HATAYAMA Daisuke wrote:
> This is the patch series to address the issue that kdump 2nd kernel
> now fails to wake up multiple CPUs.
Please explain the "now" in the above sentence. Is this a regression?
If so, what is its impact? Is this something that needs to go into 3.11
as a post-rc7 change, which means it better be hyper-critical?
-hpa
next prev parent reply other threads:[~2013-08-29 13:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 9:27 [PATCH 0/2] x86, apic: Disable BSP if boot cpu is AP HATAYAMA Daisuke
2013-08-29 9:27 ` [PATCH 1/2] x86, apic: Add boot_cpu_is_bsp() to check if boot cpu is BSP HATAYAMA Daisuke
2013-10-09 23:15 ` [tip:x86/bsp-hotplug] " tip-bot for HATAYAMA Daisuke
2013-08-29 9:28 ` [PATCH 2/2] x86, apic: Disable BSP if boot cpu is AP HATAYAMA Daisuke
2013-08-31 5:22 ` Borislav Petkov
2013-09-02 2:32 ` HATAYAMA Daisuke
2013-09-02 7:13 ` Borislav Petkov
2013-09-02 9:42 ` HATAYAMA Daisuke
2013-09-04 6:12 ` Borislav Petkov
2013-09-09 6:18 ` HATAYAMA Daisuke
2013-10-09 23:16 ` [tip:x86/bsp-hotplug] " tip-bot for HATAYAMA Daisuke
2013-10-12 17:31 ` H. Peter Anvin
2013-10-12 17:42 ` Ingo Molnar
2013-11-11 19:54 ` H. Peter Anvin
2013-11-12 10:20 ` HATAYAMA Daisuke
2013-11-12 15:35 ` H. Peter Anvin
2013-08-29 13:54 ` H. Peter Anvin [this message]
2013-08-29 23:37 ` [PATCH 0/2] " Eric W. Biederman
2013-08-30 12:48 ` Vivek Goyal
2013-08-29 23:51 ` HATAYAMA Daisuke
2013-08-30 15:43 ` H. Peter Anvin
2013-10-09 20:20 ` Vivek Goyal
2013-10-14 9:03 ` Petr Tesarik
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=521F5297.4070906@linux.intel.com \
--to=hpa@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=d.hatayama@jp.fujitsu.com \
--cc=ebiederm@xmission.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox