[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52D6C4B6.8010804@zytor.com>
Date: Wed, 15 Jan 2014 09:26:14 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Vivek Goyal <vgoyal@...hat.com>,
HATAYAMA Daisuke <d.hatayama@...fujitsu.com>
CC: hpa@...ux.intel.com, jingbai.ma@...com, kexec@...ts.infradead.org,
linux-kernel@...r.kernel.org, bp@...en8.de, ebiederm@...ssion.com,
akpm@...ux-foundation.org, fengguang.wu@...el.com
Subject: Re: [RESEND PATCH v10] x86, apic, kexec, Documentation: Add disable_cpu_apicid
kernel parameter
On 01/15/2014 09:05 AM, Vivek Goyal wrote:
>
> I think this is a reasonable approach to solve the issue. Use a command
> line to not bring up specific cpu in second kernel which can create
> problems.
>
> Acked-by: Vivek Goyal <vgoyal@...hat.com>
>
> hpa, I know you are not excited about this approach. If you made up your
> mind that this appoarch is not worth pursuing, please do suggest what
> would you like to see and we can give that a try.
>
> We want to solve this problem as on large memory machines saving dump can
> take lot of time and we want to bring up multiple cpus and speed up
> compression and save on dump time.
>
I'm not excited about kdump's reliance on the command line, since it
seems to be a neverending source of trouble, simply because the command
line is fundamentally intended as a human interface. However, this
seems relatively harmless in comparison with everything else and I am
much happier with saving the ID in the first kernel rather than trying
to guess if a currently-downed CPU is the BSP.
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists