From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx1.redhat.com ([209.132.183.28]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1g5FD0-0003sv-3b for kexec@lists.infradead.org; Wed, 26 Sep 2018 19:10:56 +0000 Date: Wed, 26 Sep 2018 15:10:18 -0400 (EDT) From: Dave Anderson Message-ID: <2052418868.38852422.1537989018012.JavaMail.zimbra@redhat.com> In-Reply-To: References: Subject: Re: [PATCH] makedumpfile/ppc64: increase MAX_PHYSMEM_BITS to > 128TB MIME-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "kexec" Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: kexec@lists.infradead.org Cc: hbathini@linux.ibm.com ----- 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 > --- > 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