linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Mahesh Jagannath Salgaonkar <mahesh@linux.vnet.ibm.com>
To: Paul Mackerras <paulus@samba.org>
Cc: Amerigo Wang <amwang@redhat.com>,
	Kexec-ml <kexec@lists.infradead.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Milton Miller <miltonm@bga.com>,
	linuxppc-dev <linuxppc-dev@ozlabs.org>,
	Randy Dunlap <rdunlap@xenotime.net>,
	Anton Blanchard <anton@samba.org>,
	Vivek Goyal <vgoyal@redhat.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [RFC PATCH v5 1/9] fadump: Add documentation for firmware-assisted dump.
Date: Sat, 10 Dec 2011 10:32:37 +0530	[thread overview]
Message-ID: <4EE2E7ED.6080202@linux.vnet.ibm.com> (raw)
In-Reply-To: <20111124223410.GB19828@bloggs.ozlabs.ibm.com>

On 11/25/2011 04:04 AM, Paul Mackerras wrote:
>> + /sys/kernel/debug/powerpc/fadump_region
>> +
>> +    This file shows the reserved memory regions if fadump is
>> +    enabled otherwise this file is empty. The output format
>> +    is:
>> +    <region>: [<start>-<end>] <reserved-size> bytes, Dumped: <dump-size>
>> +
>> +    e.g.
>> +    Contents when fadump is registered during first kernel
>> +
>> +    # cat /sys/kernel/debug/powerpc/fadump_region
>> +    CPU : [0x0000006ffb0000-0x0000006fff001f] 0x40020 bytes, Dumped: 0x0
>> +    HPTE: [0x0000006fff0020-0x0000006fff101f] 0x1000 bytes, Dumped: 0x0
>> +    DUMP: [0x0000006fff1020-0x0000007fff101f] 0x10000000 bytes, Dumped: 0x0
> 
> How come the HPTE region is only 0x1000 (4k) bytes?  The hashed page
> table (HPT) will be much bigger than this.  Is this our way of telling
> the hypervisor that we don't care about the HPT?  If so, is it
> possible to make this region 0 bytes instead of 0x1000?
> 

The firmware assisted dump registration fails with "Hardware
error (-1)" when called with HPTE dump section with size 0.

According to PAPR the size returned by ibm,configure-kernel-dump-sizes
node for HPTE dump section is a minimum size for HPTE dump section.

Though PAPR dose not mention this, but after sevaral trial and error, it
looks like the HPTE dump section is one of the mandatory
argument that needs to be passed (with non-zero size) while making
ibm,configure-kernel-dump rtas call.

Thanks,
-Mahesh.

  parent reply	other threads:[~2011-12-10  5:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-15 15:13 [RFC PATCH v5 0/9] fadump: Firmware-assisted dump support for Powerpc Mahesh J Salgaonkar
2011-11-15 15:13 ` [RFC PATCH v5 1/9] fadump: Add documentation for firmware-assisted dump Mahesh J Salgaonkar
2011-11-24 22:34   ` Paul Mackerras
2011-11-25 13:30     ` Mahesh J. Salgaonkar
2011-12-10  5:02     ` Mahesh Jagannath Salgaonkar [this message]
2011-11-15 15:13 ` [RFC PATCH v5 2/9] fadump: Reserve the memory for firmware assisted dump Mahesh J Salgaonkar
2011-11-24 23:02   ` Paul Mackerras
2011-11-28  6:21     ` Mahesh J. Salgaonkar
2011-11-15 15:13 ` [RFC PATCH v5 3/9] fadump: Register " Mahesh J Salgaonkar
2011-11-15 15:13 ` [RFC PATCH v5 4/9] fadump: Initialize elfcore header and add PT_LOAD program headers Mahesh J Salgaonkar
2011-11-15 15:14 ` [RFC PATCH v5 5/9] fadump: Convert firmware-assisted cpu state dump data into elf notes Mahesh J Salgaonkar
2011-11-15 15:14 ` [RFC PATCH v5 6/9] fadump: Add PT_NOTE program header for vmcoreinfo Mahesh J Salgaonkar
2011-11-15 15:14 ` [RFC PATCH v5 7/9] fadump: Introduce cleanup routine to invalidate /proc/vmcore Mahesh J Salgaonkar
2011-11-15 15:14 ` [RFC PATCH v5 8/9] fadump: Invalidate registration and release reserved memory for general use Mahesh J Salgaonkar
2011-11-15 15:14 ` [RFC PATCH v5 9/9] fadump: Invalidate the fadump registration during machine shutdown Mahesh J Salgaonkar
2011-11-21 12:03 ` [RFC PATCH v5 0/9] fadump: Firmware-assisted dump support for Powerpc Cong Wang

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=4EE2E7ED.6080202@linux.vnet.ibm.com \
    --to=mahesh@linux.vnet.ibm.com \
    --cc=amwang@redhat.com \
    --cc=anton@samba.org \
    --cc=ebiederm@xmission.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=miltonm@bga.com \
    --cc=paulus@samba.org \
    --cc=rdunlap@xenotime.net \
    --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).