public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Zhou Wenjian <zhouwj-fnst@cn.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
	dyoung@redhat.com, d.hatayama@jp.fujitsu.com
Subject: Re: [PATCH 1/2] Documentation: kdump: update maxcpus to nr_cpus
Date: Sat, 30 Jul 2016 10:19:59 +0800	[thread overview]
Message-ID: <20160730021959.GC2583@x1.redhat.com> (raw)
In-Reply-To: <1469762595-1085-1-git-send-email-zhouwj-fnst@cn.fujitsu.com>

On 07/29/16 at 11:23am, Zhou Wenjian wrote:
> Parameter nr_cpus is used to bring up a SMP dump-capture kernel,
> instead of the old parameter maxcpus. This commit update it in
> Documentation/kdump/kdump.txt.
> 
> Signed-off-by: Zhou Wenjian <zhouwj-fnst@cn.fujitsu.com>
> ---
>  Documentation/kdump/kdump.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/kdump/kdump.txt b/Documentation/kdump/kdump.txt
> index 88ff63d..9a77247 100644
> --- a/Documentation/kdump/kdump.txt
> +++ b/Documentation/kdump/kdump.txt
> @@ -392,7 +392,7 @@ Notes on loading the dump-capture kernel:
>  
>  * We generally don' have to bring up a SMP kernel just to capture the
>    dump. Hence generally it is useful either to build a UP dump-capture
> -  kernel or specify maxcpus=1 option while loading dump-capture kernel.
> +  kernel or specify nr_cpus=1 option while loading dump-capture kernel.


IIRC, ARCHes like ppc don't have nr_cpus yet, maxpcus is necessary. So
either you explicitly tell which can use nr_cpus and which can only use
maxcpus option, or drop this patch for now.

>  
>  * For s390x there are two kdump modes: If a ELF header is specified with
>    the elfcorehdr= kernel parameter, it is used by the kdump kernel as it
> -- 
> 1.8.3.1
> 
> 
> 

      parent reply	other threads:[~2016-07-30  2:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29  3:23 [PATCH 1/2] Documentation: kdump: update maxcpus to nr_cpus Zhou Wenjian
2016-07-29  3:23 ` [PATCH 2/2] Documentation: kdump: add description of bringing up SMP dump-capture kernel Zhou Wenjian
2016-07-30  2:19 ` Baoquan He [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=20160730021959.GC2583@x1.redhat.com \
    --to=bhe@redhat.com \
    --cc=d.hatayama@jp.fujitsu.com \
    --cc=dyoung@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zhouwj-fnst@cn.fujitsu.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