From: Pratyush Anand <panand@redhat.com>
To: Timur Tabi <timur@codeaurora.org>
Cc: virajm@codeaurora.org, ats-kumagai@wm.jp.nec.com,
asamson@codeaurora.org, kexec@lists.infradead.org
Subject: Re: [PATCH] makedumpfile: Support ARM64
Date: Wed, 24 Jun 2015 09:02:41 +0530 [thread overview]
Message-ID: <20150624033241.GA22348@localhost.localdomain> (raw)
In-Reply-To: <CAOZdJXWjZmL_K=FmvBU=U3VSDY9R4AucFU16v8CAgQCEe8HYDg@mail.gmail.com>
Hi Timur,
On 23/06/2015:06:19:01 PM, Timur Tabi wrote:
> On Fri, May 15, 2015 at 1:30 PM, Pratyush Anand <panand@redhat.com> wrote:
> > Patch adds support for ARM64 in makedumpfile. It takes care of vmalloc,
> > vmemmap, module and directly map kernel memory region's translation.
> >
> > Currently we only support 2 leverl 64K pages and VA_BITS as 42. Support
> > to find these machine specific parameters dynamically and then to act
> > accordingly can be added latter.
>
> So ARM64 kernels are typically compiled with 3-level 4KB pages:
>
> CONFIG_ARM64_4K_PAGES=y
> # CONFIG_ARM64_64K_PAGES is not set
> CONFIG_ARM64_VA_BITS_39=y
> # CONFIG_ARM64_VA_BITS_48 is not set
> CONFIG_ARM64_VA_BITS=39
>
> Does this mean that your patch won't work on such a kernel? If so, do
Yes, it will not work with above kernel.
> you have any plans to add support for 4K 3-level pages?
I can try to find out some time in weekend to refactor arm64 code
and then add 3 level, 4K support. May be I will need a Tested-by.
~Pratyush
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2015-06-24 3:33 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 [this message]
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
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=20150624033241.GA22348@localhost.localdomain \
--to=panand@redhat.com \
--cc=asamson@codeaurora.org \
--cc=ats-kumagai@wm.jp.nec.com \
--cc=kexec@lists.infradead.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