From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (ozlabs.org [IPv6:2401:3900:2:1::2]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 3wKDrc0ZcQzDqCL for ; Sat, 6 May 2017 00:32:48 +1000 (AEST) Received: from ozlabs.org (ozlabs.org [IPv6:2401:3900:2:1::2]) by bilbo.ozlabs.org (Postfix) with ESMTP id 3wKDrb6t75z8tBf for ; Sat, 6 May 2017 00:32:47 +1000 (AEST) Received: from mx0a-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com [148.163.158.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ozlabs.org (Postfix) with ESMTPS id 3wKDrb2qLyz9s7f for ; Sat, 6 May 2017 00:32:47 +1000 (AEST) Received: from pps.filterd (m0098413.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v45ET24T087306 for ; Fri, 5 May 2017 10:32:41 -0400 Received: from e23smtp08.au.ibm.com (e23smtp08.au.ibm.com [202.81.31.141]) by mx0b-001b2d01.pphosted.com with ESMTP id 2a8tphhqe4-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for ; Fri, 05 May 2017 10:32:40 -0400 Received: from localhost by e23smtp08.au.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Sat, 6 May 2017 00:32:34 +1000 Received: from d23av01.au.ibm.com (d23av01.au.ibm.com [9.190.234.96]) by d23relay09.au.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v45EWNGt4456724 for ; Sat, 6 May 2017 00:32:31 +1000 Received: from d23av01.au.ibm.com (localhost [127.0.0.1]) by d23av01.au.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id v45EVwVP015492 for ; Sat, 6 May 2017 00:31:58 +1000 Subject: Re: [PATCH 2/2] powerpc/fadump: avoid holes in boot memory area when fadump is registered To: Pingfan Liu References: <149392041651.10802.10097444663269312695.stgit@hbathini.in.ibm.com> <149392044508.10802.11008391107873058533.stgit@hbathini.in.ibm.com> <935304973.5269011.1493984598730.JavaMail.zimbra@redhat.com> Cc: Michael Ellerman , linuxppc-dev , Mahesh J Salgaonkar From: Hari Bathini Date: Fri, 5 May 2017 20:01:27 +0530 MIME-Version: 1.0 In-Reply-To: <935304973.5269011.1493984598730.JavaMail.zimbra@redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed Message-Id: List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Friday 05 May 2017 05:13 PM, Pingfan Liu wrote: > > > > ----- Original Message ----- >> From: "Hari Bathini" >> To: "Michael Ellerman" >> Cc: "linuxppc-dev" , "Pingfan Liu" , "Mahesh J Salgaonkar" >> >> Sent: Friday, May 5, 2017 1:54:05 AM >> Subject: [PATCH 2/2] powerpc/fadump: avoid holes in boot memory area when fadump is registered >> >> To register fadump, boot memory area - the size of low memory chunk that >> is required for a kernel to boot successfully when booted with restricted >> memory, is assumed to have no holes. But this memory area is currently > The continuous is required by fadump code, not by the firmware itself, right? > Hmmm... Firmware takes a memory region,what we are calling boot memory area, as input to be backed up at the time of crash. The same memory region is used by kernel to boot after the crash. Firmware doesn't allow holes in this memory region at the time of registering... Thanks Hari