From: Jerry.Hoemann@hp.com
To: Vivek Goyal <vgoyal@redhat.com>
Cc: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>,
"H. Peter Anvin" <hpa@linux.intel.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 v9] x86, apic, kexec, Documentation: Add disable_cpu_apic kernel parameter
Date: Wed, 4 Dec 2013 13:21:04 -0700 [thread overview]
Message-ID: <20131204202104.GA6348@anatevka.fc.hp.com> (raw)
In-Reply-To: <20131203152536.GE4251@redhat.com>
On Tue, Dec 03, 2013 at 10:25:36AM -0500, Vivek Goyal wrote:
>
> Hi Hatayama,
>
> We are almost there. A minor nit. Why have we specified KEXEC here. This
> parameter disabled_cpu_apicid does not seem to dependon CONFIG_KEXEC?
>
> Jerry, this patch looks good to me. Does it work on your system?
>
> Thanks
> Vivek
Vivek, Hatayama,
I've back ported v9 of this patch to 2.6.32 and 3.0.80 based kernels to
test with existing distros.
I've tested on our smaller prototype server specifying nr_cpus=8/maxcpus=8
to the capture kernel. One hundred iterations (echo c > /proc/sysrq-trigger)
varying target cpu and system load to each kernel.
The 2.6.32 based distro kernel showed the < 5% soft lockup
(still unresolved) during boot of capture kernel. This is
something i've seen on all versions of the patch that i've tested.
The 3.0.80 based distro kernel has had zero failures.
I have not had a chance to test upstream kernels or on
our larger prototype configuration.
We still plan to test on our larger prototype. Testing of
prior versions of the patch on the larger systems didn't show
problems w/ this functionality and I don't anticipate we'll
find anything this time either.
I am okay with this patch being accepted upstream and working
the intermittent 2.6.32 failures separately.
Jerry
--
----------------------------------------------------------------------------
Jerry Hoemann Software Engineer Hewlett-Packard
3404 E Harmony Rd. MS 57 phone: (970) 898-1022
Ft. Collins, CO 80528 FAX: (970) 898-XXXX
email: jerry.hoemann@hp.com
----------------------------------------------------------------------------
prev parent reply other threads:[~2013-12-04 20:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 1:32 HATAYAMA Daisuke
2013-12-03 15:25 ` Vivek Goyal
2013-12-04 3:08 ` HATAYAMA Daisuke
2013-12-04 6:24 ` HATAYAMA Daisuke
2013-12-04 17:36 ` Vivek Goyal
2013-12-04 20:21 ` Jerry.Hoemann [this message]
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=20131204202104.GA6348@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome