From: "Yu, Fenghua" <fenghua.yu@intel.com> To: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "kexec@lists.infradead.org" <kexec@lists.infradead.org>, "x86@kernel.org" <x86@kernel.org> Cc: "mingo@elte.hu" <mingo@elte.hu>, "tglx@linutronix.de" <tglx@linutronix.de>, "hpa@zytor.com" <hpa@zytor.com>, "Brown, Len" <len.brown@intel.com>, "vgoyal@redhat.com" <vgoyal@redhat.com>, "ebiederm@xmission.com" <ebiederm@xmission.com>, "grant.likely@secretlab.ca" <grant.likely@secretlab.ca>, "rob.herring@calxeda.com" <rob.herring@calxeda.com> Subject: RE: [PATCH v1 0/2] x86, apic: Disable BSP if boot cpu is AP Date: Tue, 16 Oct 2012 04:51:36 +0000 [thread overview] Message-ID: <3E5A0FA7E9CA944F9D5414FEC6C7122030B0DD68@ORSMSX105.amr.corp.intel.com> (raw) In-Reply-To: <20121016043357.20003.5885.stgit@localhost6.localdomain6> [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain; charset="utf-8", Size: 2564 bytes --] > -----Original Message----- > From: HATAYAMA Daisuke [mailto:d.hatayama@jp.fujitsu.com] > Sent: Monday, October 15, 2012 9:35 PM > To: linux-kernel@vger.kernel.org; kexec@lists.infradead.org; > x86@kernel.org > Cc: mingo@elte.hu; tglx@linutronix.de; hpa@zytor.com; Brown, Len; Yu, > Fenghua; vgoyal@redhat.com; ebiederm@xmission.com; > grant.likely@secretlab.ca; rob.herring@calxeda.com; > d.hatayama@jp.fujitsu.com > Subject: [PATCH v1 0/2] x86, apic: Disable BSP if boot cpu is AP > > Multiple CPUs are useful for CPU-bound processing like compression and > I do want to use compression to generate crash dump quickly. But now > we cannot wakeup the 2nd and later cpus in the kdump 2nd kernel if > crash happens on AP. If crash happens on AP, kexec enters the 2nd > kernel with the AP, and there BSP in the 1st kernel is expected to be > haling in the 1st kernel or possibly in any fatal system error state. > > To wake up AP, we use the method called INIT-INIT-SIPI. INIT causes > BSP to jump into BIOS init code. A typical visible behaviour is hang > or immediate reset, depending on the BIOS init code. > > AP can be initiated by INIT even in a fatal state: MP spec explains > that processor-specific INIT can be used to recover AP from a fatal > system error. On the other hand, there's no method for BSP to recover; > it might be possible to do so by NMI plus any hand-coded reset code > that is carefully designed, but at least I have no idea in this > direction now. In my BSP hotplug patchset, BPS is waken up by NMI. The patchset is not in tip tree yet. BSP hotplug patchset can be found at https://lkml.org/lkml/2012/10/12/336 > > Therefore, the idea I do in this patch set is simply to disable BSP if > vboot cpu is AP. > The BSP hotplug patchset will be useful for you goal. With the BSP hotplug patcheset, you can wake up BSP and don't need to disable it. > My motivation is to use multiple CPUs in order to quickly generate > crash dump on the machine with huge amount of memory. I assume such > machine tends to also have a lot of CPUs. So disabling one CPU would > be no problem. Luckily you don't need to disable any CPU to archive your goal with the BSP hotplug pachest:) On a dual core/single thread machine, this means you get 100% performance boost with BSP's help. Plus crash dump kernel code is better structured by not treating BSP specially. Thanks. -Fenghua ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
WARNING: multiple messages have this Message-ID (diff)
From: "Yu, Fenghua" <fenghua.yu@intel.com> To: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "kexec@lists.infradead.org" <kexec@lists.infradead.org>, "x86@kernel.org" <x86@kernel.org> Cc: "Brown, Len" <len.brown@intel.com>, "rob.herring@calxeda.com" <rob.herring@calxeda.com>, "grant.likely@secretlab.ca" <grant.likely@secretlab.ca>, "ebiederm@xmission.com" <ebiederm@xmission.com>, "hpa@zytor.com" <hpa@zytor.com>, "mingo@elte.hu" <mingo@elte.hu>, "tglx@linutronix.de" <tglx@linutronix.de>, "vgoyal@redhat.com" <vgoyal@redhat.com> Subject: RE: [PATCH v1 0/2] x86, apic: Disable BSP if boot cpu is AP Date: Tue, 16 Oct 2012 04:51:36 +0000 [thread overview] Message-ID: <3E5A0FA7E9CA944F9D5414FEC6C7122030B0DD68@ORSMSX105.amr.corp.intel.com> (raw) In-Reply-To: <20121016043357.20003.5885.stgit@localhost6.localdomain6> > -----Original Message----- > From: HATAYAMA Daisuke [mailto:d.hatayama@jp.fujitsu.com] > Sent: Monday, October 15, 2012 9:35 PM > To: linux-kernel@vger.kernel.org; kexec@lists.infradead.org; > x86@kernel.org > Cc: mingo@elte.hu; tglx@linutronix.de; hpa@zytor.com; Brown, Len; Yu, > Fenghua; vgoyal@redhat.com; ebiederm@xmission.com; > grant.likely@secretlab.ca; rob.herring@calxeda.com; > d.hatayama@jp.fujitsu.com > Subject: [PATCH v1 0/2] x86, apic: Disable BSP if boot cpu is AP > > Multiple CPUs are useful for CPU-bound processing like compression and > I do want to use compression to generate crash dump quickly. But now > we cannot wakeup the 2nd and later cpus in the kdump 2nd kernel if > crash happens on AP. If crash happens on AP, kexec enters the 2nd > kernel with the AP, and there BSP in the 1st kernel is expected to be > haling in the 1st kernel or possibly in any fatal system error state. > > To wake up AP, we use the method called INIT-INIT-SIPI. INIT causes > BSP to jump into BIOS init code. A typical visible behaviour is hang > or immediate reset, depending on the BIOS init code. > > AP can be initiated by INIT even in a fatal state: MP spec explains > that processor-specific INIT can be used to recover AP from a fatal > system error. On the other hand, there's no method for BSP to recover; > it might be possible to do so by NMI plus any hand-coded reset code > that is carefully designed, but at least I have no idea in this > direction now. In my BSP hotplug patchset, BPS is waken up by NMI. The patchset is not in tip tree yet. BSP hotplug patchset can be found at https://lkml.org/lkml/2012/10/12/336 > > Therefore, the idea I do in this patch set is simply to disable BSP if > vboot cpu is AP. > The BSP hotplug patchset will be useful for you goal. With the BSP hotplug patcheset, you can wake up BSP and don't need to disable it. > My motivation is to use multiple CPUs in order to quickly generate > crash dump on the machine with huge amount of memory. I assume such > machine tends to also have a lot of CPUs. So disabling one CPU would > be no problem. Luckily you don't need to disable any CPU to archive your goal with the BSP hotplug pachest:) On a dual core/single thread machine, this means you get 100% performance boost with BSP's help. Plus crash dump kernel code is better structured by not treating BSP specially. Thanks. -Fenghua _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2012-10-16 4:51 UTC|newest] Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-16 4:35 [PATCH v1 0/2] x86, apic: Disable BSP if boot cpu is AP HATAYAMA Daisuke 2012-10-16 4:35 ` HATAYAMA Daisuke 2012-10-16 4:35 ` [PATCH v1 1/2] x86, apic: Introduce boot_cpu_is_bsp indicating whether boot cpu is BSP or not HATAYAMA Daisuke 2012-10-16 4:35 ` HATAYAMA Daisuke 2012-10-16 4:35 ` [PATCH v1 2/2] x86, apic: Disable BSP if boot cpu is AP HATAYAMA Daisuke 2012-10-16 4:35 ` HATAYAMA Daisuke 2012-10-22 20:04 ` Eric W. Biederman 2012-10-22 20:04 ` Eric W. Biederman 2012-10-22 20:16 ` H. Peter Anvin 2012-10-22 20:16 ` H. Peter Anvin 2012-10-22 20:31 ` Eric W. Biederman 2012-10-22 20:31 ` Eric W. Biederman 2012-10-22 20:33 ` H. Peter Anvin 2012-10-22 20:33 ` H. Peter Anvin 2012-10-22 20:38 ` H. Peter Anvin 2012-10-22 20:38 ` H. Peter Anvin 2012-10-22 20:43 ` Eric W. Biederman 2012-10-22 20:43 ` Eric W. Biederman 2012-10-22 20:47 ` H. Peter Anvin 2012-10-22 20:47 ` H. Peter Anvin 2012-10-22 21:29 ` Eric W. Biederman 2012-10-22 21:29 ` Eric W. Biederman 2012-10-23 0:35 ` H. Peter Anvin 2012-10-23 0:35 ` H. Peter Anvin 2012-10-26 3:24 ` HATAYAMA Daisuke 2012-10-26 3:24 ` HATAYAMA Daisuke 2012-10-26 4:13 ` Eric W. Biederman 2012-10-26 4:13 ` Eric W. Biederman 2013-03-11 1:07 ` HATAYAMA Daisuke 2013-03-11 1:07 ` HATAYAMA Daisuke 2013-03-11 2:13 ` HATAYAMA Daisuke 2013-03-11 2:13 ` HATAYAMA Daisuke 2013-03-11 4:11 ` H. Peter Anvin 2013-03-11 4:11 ` H. Peter Anvin 2012-10-16 4:51 ` Yu, Fenghua [this message] 2012-10-16 4:51 ` [PATCH v1 0/2] " Yu, Fenghua 2012-10-16 5:03 ` HATAYAMA Daisuke 2012-10-16 5:03 ` HATAYAMA Daisuke 2012-10-16 5:14 ` Yu, Fenghua 2012-10-16 5:14 ` Yu, Fenghua 2012-10-16 6:38 ` HATAYAMA Daisuke 2012-10-16 6:38 ` HATAYAMA Daisuke 2012-10-22 16:02 ` H. Peter Anvin 2012-10-22 16:02 ` H. Peter Anvin 2012-10-16 5:15 ` HATAYAMA Daisuke 2012-10-16 5:15 ` HATAYAMA Daisuke 2012-10-17 14:12 ` Vivek Goyal 2012-10-17 14:12 ` Vivek Goyal 2012-10-18 3:08 ` HATAYAMA Daisuke 2012-10-18 3:08 ` HATAYAMA Daisuke 2012-10-18 14:14 ` Vivek Goyal 2012-10-18 14:14 ` Vivek Goyal 2012-10-19 3:20 ` HATAYAMA Daisuke 2012-10-19 3:20 ` HATAYAMA Daisuke 2012-10-19 15:17 ` Vivek Goyal 2012-10-19 15:17 ` Vivek Goyal 2012-10-22 6:32 ` HATAYAMA Daisuke 2012-10-22 6:32 ` HATAYAMA Daisuke 2012-10-22 18:37 ` Vivek Goyal 2012-10-22 18:37 ` Vivek Goyal 2012-10-22 17:10 ` Michael Holzheu 2012-10-22 17:10 ` Michael Holzheu
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=3E5A0FA7E9CA944F9D5414FEC6C7122030B0DD68@ORSMSX105.amr.corp.intel.com \ --to=fenghua.yu@intel.com \ --cc=d.hatayama@jp.fujitsu.com \ --cc=ebiederm@xmission.com \ --cc=grant.likely@secretlab.ca \ --cc=hpa@zytor.com \ --cc=kexec@lists.infradead.org \ --cc=len.brown@intel.com \ --cc=linux-kernel@vger.kernel.org \ --cc=mingo@elte.hu \ --cc=rob.herring@calxeda.com \ --cc=tglx@linutronix.de \ --cc=vgoyal@redhat.com \ --cc=x86@kernel.org \ /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: linkBe 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.