From: Hari Bathini <hbathini@linux.vnet.ibm.com>
To: Pingfan Liu <piliu@redhat.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
linuxppc-dev <linuxppc-dev@ozlabs.org>,
Mahesh J Salgaonkar <mahesh@linux.vnet.ibm.com>
Subject: Re: [PATCH 2/2] powerpc/fadump: avoid holes in boot memory area when fadump is registered
Date: Fri, 5 May 2017 20:01:27 +0530 [thread overview]
Message-ID: <f196024d-a78c-c30f-fb51-02d9cffa16c2@linux.vnet.ibm.com> (raw)
In-Reply-To: <935304973.5269011.1493984598730.JavaMail.zimbra@redhat.com>
On Friday 05 May 2017 05:13 PM, Pingfan Liu wrote:
>
>
>
> ----- Original Message -----
>> From: "Hari Bathini" <hbathini@linux.vnet.ibm.com>
>> To: "Michael Ellerman" <mpe@ellerman.id.au>
>> Cc: "linuxppc-dev" <linuxppc-dev@ozlabs.org>, "Pingfan Liu" <piliu@redhat.com>, "Mahesh J Salgaonkar"
>> <mahesh@linux.vnet.ibm.com>
>> 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
next prev parent reply other threads:[~2017-05-05 14:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 17:53 [PATCH 1/2] powerpc/fadump: avoid duplicates in crash memory ranges Hari Bathini
2017-05-04 17:54 ` [PATCH 2/2] powerpc/fadump: avoid holes in boot memory area when fadump is registered Hari Bathini
2017-05-05 6:54 ` Mahesh Jagannath Salgaonkar
2017-05-05 11:43 ` Pingfan Liu
2017-05-05 14:31 ` Hari Bathini [this message]
2017-05-05 6:52 ` [PATCH 1/2] powerpc/fadump: avoid duplicates in crash memory ranges Mahesh Jagannath Salgaonkar
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=f196024d-a78c-c30f-fb51-02d9cffa16c2@linux.vnet.ibm.com \
--to=hbathini@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=piliu@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;
as well as URLs for NNTP newsgroup(s).