linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Hari Bathini <hbathini@linux.vnet.ibm.com>
To: Mahesh Jagannath Salgaonkar <mahesh@linux.vnet.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH v1 1/2] fadump: reduce memory consumption for capture kernel
Date: Tue, 7 Feb 2017 20:27:37 +0530	[thread overview]
Message-ID: <cffce11c-6037-4c9b-3dd1-8c7102790b6c@linux.vnet.ibm.com> (raw)
In-Reply-To: <3d19b81e-1ea6-cdcf-cb28-ebd2c17d7378@linux.vnet.ibm.com>

Hi Mahesh,


On Tuesday 31 January 2017 01:05 AM, Mahesh Jagannath Salgaonkar wrote:
> On 01/30/2017 10:14 PM, Hari Bathini wrote:
>> In case of fadump, capture (fadump) kernel boots like a normal kernel.
>> While this has its advantages, the capture kernel would initialize all
>> the components like normal kernel, which may not necessarily be needed
>> for a typical dump capture kernel. So, fadump capture kernel ends up
>> needing more memory than a typical (read kdump) capture kernel to boot.
...
>> +#define FADUMP_FORMAT_VERSION	0x00000002
> Why 0x0002 ? Does Phyp now support new version of dump format ? We
> should be more careful not to break backward compatibility.

Dump format version has not changed in Phyp. Undone the change in v2
to keep backward compatibility intact.

>> +static ssize_t fadump_params_show(struct kobject *kobj,
>> +				   struct kobj_attribute *attr,
>> +				   char *buf)
>> +{
>> +	return sprintf(buf, "%s\n",
>> +		get_fadump_params_buf(__va(fw_dump.handover_area_start)));
> May be we should show current cmdline + fadump append params.

I think it is better to display only append parameters as current 
cmdline parameters
may not be accurate always?

Thanks
Hari

  reply	other threads:[~2017-02-07 14:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-30 16:44 [PATCH v1 1/2] fadump: reduce memory consumption for capture kernel Hari Bathini
2017-01-30 16:44 ` [PATCH v1 2/2] fadump: update documentation about introduction of handover area Hari Bathini
2017-01-30 19:35 ` [PATCH v1 1/2] fadump: reduce memory consumption for capture kernel Mahesh Jagannath Salgaonkar
2017-02-07 14:57   ` Hari Bathini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-01-30 16:49 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=cffce11c-6037-4c9b-3dd1-8c7102790b6c@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 \
    /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).