Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pratyush Anand <panand@redhat.com>
To: sgoel@codeaurora.org
Cc: virajm@codeaurora.org, Timur Tabi <timur@codeaurora.org>,
	Azriel Samson <asamson@codeaurora.org>,
	kexec@lists.infradead.org, ats-kumagai@wm.jp.nec.com
Subject: Re: [PATCH] makedumpfile: Support ARM64
Date: Fri, 21 Aug 2015 09:14:33 +0530	[thread overview]
Message-ID: <20150821034433.GB26132@dhcppc13.redhat.com> (raw)
In-Reply-To: <cd279166af08eba11be211481f319ab8.squirrel@www.codeaurora.org>

Hi Sameer,

On 20/08/2015:04:11:24 PM, sgoel@codeaurora.org wrote:
> Hi Pratush,
> I have made the change now.
> 
> The reason for changing the KVBASE was to get non zero value for mem_map
> as seen from the crash tool. If KVBASE stays at page offset we do not get
> into the function that looks for the free pages.

OK.. I made the change for KVBASE and pushed it to my github repo.

> 
> After looking at the page usage using the crash tool it seems that ~80% of
> the pages are free.
> 
> Maybe there is something else that I am missing here. The page look up
> fails when writing the crashdump file.

Not sure if you can share the output with --message-level 31, but do you see any
thing susceptible there?

# makedumpfile -l --message-level 31 rawvmcore makedumpfilevmcore

Can you compare "Virtual kernel memory layout:" print of Linux kernel boot with
makedumpfile print for page_offset, vmalloc_start, vmemmap_start etc, and see if
they match?

They should match.

~Pratyush

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2015-08-21  3:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15 18:30 [PATCH] makedumpfile: Support ARM64 Pratyush Anand
2015-05-19  7:26 ` Atsushi Kumagai
2015-06-23 23:19 ` Timur Tabi
2015-06-24  3:32   ` Pratyush Anand
2015-06-24  3:36     ` Timur Tabi
2015-06-27  8:22       ` Pratyush Anand
2015-07-01 18:42         ` Azriel Samson
2015-07-03  4:32           ` Pratyush Anand
2015-07-08 23:03             ` Azriel Samson
2015-08-18 17:18               ` Azriel Samson
2015-08-19 23:16                 ` sgoel
2015-08-20 11:21                   ` Pratyush Anand
2015-08-20 16:11                     ` sgoel
2015-08-21  3:44                       ` Pratyush Anand [this message]
2015-08-21  7:25                         ` Atsushi Kumagai
2015-08-21 20:37                         ` sgoel
2015-08-22  3:54                           ` Pratyush Anand
2015-08-24 18:17                             ` sgoel
2015-08-25  0:21                               ` sgoel
2015-09-08 22:32                                 ` sgoel
2015-09-11 16:52                                   ` Pratyush Anand
2015-09-14 16:02                                     ` sgoel

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=20150821034433.GB26132@dhcppc13.redhat.com \
    --to=panand@redhat.com \
    --cc=asamson@codeaurora.org \
    --cc=ats-kumagai@wm.jp.nec.com \
    --cc=kexec@lists.infradead.org \
    --cc=sgoel@codeaurora.org \
    --cc=timur@codeaurora.org \
    --cc=virajm@codeaurora.org \
    /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