From: Hari Bathini <hbathini@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
rusty@rustcorp.com.au, ebiederm@xmission.com, vgoyal@redhat.com,
linuxppc-dev <linuxppc-dev@ozlabs.org>
Cc: Mahesh J Salgaonkar <mahesh@linux.vnet.ibm.com>,
kexec@lists.infradead.org, lkml <linux-kernel@vger.kernel.org>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>
Subject: Re: [RESEND][PATCH v2 2/2] powerpc/fadump: parse fadump reserve memory size based on memory range
Date: Fri, 5 Aug 2016 00:23:26 +0530 [thread overview]
Message-ID: <ef95923f-56b6-b4f1-94a2-555f7df32629@linux.vnet.ibm.com> (raw)
In-Reply-To: <87h9b0g953.fsf@concordia.ellerman.id.au>
On Thursday 04 August 2016 03:15 PM, Michael Ellerman wrote:
> Hari Bathini <hbathini@linux.vnet.ibm.com> writes:
> ...
>> /**
>> * fadump_calculate_reserve_size(): reserve variable boot area 5% of System RAM
>> *
>> @@ -212,12 +262,17 @@ static inline unsigned long fadump_calculate_reserve_size(void)
>> {
>> unsigned long size;
>>
>> + /* sets fw_dump.reserve_bootvar */
>> + parse_fadump_reserve_mem();
>> +
>> /*
>> * Check if the size is specified through fadump_reserve_mem= cmdline
>> * option. If yes, then use that.
>> */
>> if (fw_dump.reserve_bootvar)
>> return fw_dump.reserve_bootvar;
>> + else
>> + printk(KERN_INFO "fadump: calculating default boot size\n");
>>
>> /* divide by 20 to get 5% of value */
>> size = memblock_end_of_DRAM() / 20;
> The code already knows how to reserve 5% based on the size of the machine's
> memory, as long as no commandline parameter is passed. So why can't we
> just use that logic?
Hi Michael,
That is the default value reserved but not a good enough value for
every case. It is a bit difficult to come up with a robust formula
that works for every case as new kernel changes could make the
values obsolete. But it won't be all that difficult to find values that
work for different memory ranges for a given kernel version.
Passing that as range based input with "fadump_reserve_mem"
parameter would work for every memory configuration on a
given system, which is what this patch is trying to provide..
Thanks
Hari
> cheers
>
next prev parent reply other threads:[~2016-08-04 18:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 19:32 [RESEND][PATCH v2 0/2] powerpc/fadump: support memory range syntax for fadump memory reservation Hari Bathini
2016-08-03 19:33 ` [RESEND][PATCH v2 1/2] kexec: refactor code parsing size based on memory range Hari Bathini
2016-08-04 9:26 ` Dave Young
2016-08-04 19:04 ` Hari Bathini
2016-08-03 19:33 ` [RESEND][PATCH v2 2/2] powerpc/fadump: parse fadump reserve memory " Hari Bathini
2016-08-04 9:45 ` Michael Ellerman
2016-08-04 18:53 ` Hari Bathini [this message]
2016-08-08 8:15 ` Hari Bathini
2016-08-08 8:56 ` Michael Ellerman
2016-08-08 9:25 ` Hari Bathini
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=ef95923f-56b6-b4f1-94a2-555f7df32629@linux.vnet.ibm.com \
--to=hbathini@linux.vnet.ibm.com \
--cc=ananth@in.ibm.com \
--cc=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=rusty@rustcorp.com.au \
--cc=vgoyal@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).