Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Anderson <anderson@redhat.com>
To: kexec@lists.infradead.org
Cc: hbathini@linux.ibm.com
Subject: Re: [PATCH] makedumpfile/ppc64: increase MAX_PHYSMEM_BITS to > 128TB
Date: Wed, 26 Sep 2018 15:10:18 -0400 (EDT)	[thread overview]
Message-ID: <2052418868.38852422.1537989018012.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <mailman.7.1537988404.27860.kexec@lists.infradead.org>


----- Original Message -----
>
> * Required for kernel 4.19
> 
> With kernel commit 7d4340bb92a9 ("powerpc/mm: Increase MAX_PHYSMEM_BITS
> to 128TB with SPARSEMEM_VMEMMAP config"), MAX_PHYSMEM_BITS is bumped up
> to 47. Make the appropriate update here.
> 
> Signed-off-by: Hari Bathini <hbathini@linux.ibm.com>
> ---
>  arch/ppc64.c   |    5 +++++
>  makedumpfile.h |    1 +
>  2 files changed, 6 insertions(+)
> 
> diff --git a/arch/ppc64.c b/arch/ppc64.c
> index 8b6f7d5..947a125 100644
> --- a/arch/ppc64.c
> +++ b/arch/ppc64.c
> @@ -481,6 +481,11 @@ set_ppc64_max_physmem_bits(void)
>  		|| (array_len == (NR_MEM_SECTIONS() / _SECTIONS_PER_ROOT())))
>  		return TRUE;
>  
> +	info->max_physmem_bits  = _MAX_PHYSMEM_BITS_4_19;
> +	if ((array_len == (NR_MEM_SECTIONS() / _SECTIONS_PER_ROOT_EXTREME()))
> +		|| (array_len == (NR_MEM_SECTIONS() / _SECTIONS_PER_ROOT())))
> +		return TRUE;
> +
>  	return FALSE;
>  }
>  
> diff --git a/makedumpfile.h b/makedumpfile.h
> index d1fcd87..46ebe2e 100644
> --- a/makedumpfile.h
> +++ b/makedumpfile.h
> @@ -673,6 +673,7 @@ unsigned long get_kvbase_arm64(void);
>  #define _SECTION_SIZE_BITS	(24)
>  #define _MAX_PHYSMEM_BITS_ORIG  (44)
>  #define _MAX_PHYSMEM_BITS_3_7   (46)
> +#define _MAX_PHYSMEM_BITS_4_19  (47)
>  #define REGION_SHIFT            (60UL)
>  #define VMEMMAP_REGION_ID       (0xfUL)

Hari,

Do you have an accompanying crash utility patch coming along?

Thanks,
  Dave


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

       reply	other threads:[~2018-09-26 19:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.7.1537988404.27860.kexec@lists.infradead.org>
2018-09-26 19:10 ` Dave Anderson [this message]
2018-09-26 19:42   ` [PATCH] makedumpfile/ppc64: increase MAX_PHYSMEM_BITS to > 128TB Hari Bathini
2018-09-26 16:56 [PATCH] makedumpfile/ppc64: increase MAX_PHYSMEM_BITS to 128TB Hari Bathini
2018-09-26 20:21 ` Kazuhito Hagio

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=2052418868.38852422.1537989018012.JavaMail.zimbra@redhat.com \
    --to=anderson@redhat.com \
    --cc=hbathini@linux.ibm.com \
    --cc=kexec@lists.infradead.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: 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