From: Haren Myneni <haren@us.ibm.com>
To: michael@ellerman.id.au
Cc: linuxppc-dev@ozlabs.org, "Sachin P. Sant" <sachinp@in.ibm.com>
Subject: Re: [PATCH] kdump : Support kernels having 64k page size.
Date: Tue, 05 Sep 2006 23:13:20 -0700 [thread overview]
Message-ID: <44FE6700.8080504@us.ibm.com> (raw)
In-Reply-To: <1157511577.3661.7.camel@localhost.localdomain>
Michael Ellerman wrote:
>On Wed, 2006-09-06 at 05:56 +0530, Sachin P. Sant wrote:
>
>
>>The following kernel patch [ along with a patch to kexec tools posted
>>seperately ]
>>is required to generate proper core files using kdump on ppc64.
>>
>>
>
>Hi Sachin,
>
>Can you provide some more explanation? It's not clear to me why this is
>necessary.
>
>thanks
>
>
>
At present we are doing the backup of 32K. Thus created one ELF PT_LOAD
segment for this region.
But, in the case of 64K page size, second segments starts at 32K and the
first one is not page aligned. __ioremap() (crash_dump.c) getting
failed if pfn = 0 which is the case for the second PT_LOAD segment. We
did not hit this issue for 4K page size because the the first page (32K
backup) is copied to second kernel memory and thus referencing with the
second kernel pfn.
Here the fix is, backup regions size is max(PAGE_SIZE, 32K) so that
at least one page will be part of backup ELF segment. Drawback here is,
we will end up 32K more for backup for 64K page size.
It can also be fixed in copy_oldmem_page() (crash_dump.c), but first
PT_LOAD segment is not page aligned:
if (pfn > 0)
vaddr = __ioremap(pfn << PAGE_SHIFT, PAGE_SIZE, 0);
else
vaddr = __va(pfn << PAGE_SHIFT);
Thanks
Haren
>------------------------------------------------------------------------
>
>_______________________________________________
>Linuxppc-dev mailing list
>Linuxppc-dev@ozlabs.org
>https://ozlabs.org/mailman/listinfo/linuxppc-dev
>
next prev parent reply other threads:[~2006-09-06 6:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-06 0:26 [PATCH] kdump : Support kernels having 64k page size Sachin P. Sant
2006-09-06 2:59 ` Michael Ellerman
2006-09-06 6:13 ` Haren Myneni [this message]
2006-09-07 0:51 ` Benjamin Herrenschmidt
2006-09-08 1:00 ` Sachin P. Sant
2006-09-08 1:08 ` Benjamin Herrenschmidt
2006-09-08 2:29 ` Sachin P. Sant
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=44FE6700.8080504@us.ibm.com \
--to=haren@us.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=sachinp@in.ibm.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).