From: sgoel@codeaurora.org
To: Pratyush Anand <pratyush.anand@gmail.com>
Cc: Pratyush Anand <panand@redhat.com>,
Timur Tabi <timur@codeaurora.org>,
Azriel Samson <asamson@codeaurora.org>,
kexec@lists.infradead.org, sgoel@codeaurora.org,
virajm@codeaurora.org, ats-kumagai@wm.jp.nec.com
Subject: Re: [PATCH] makedumpfile: Support ARM64
Date: Mon, 14 Sep 2015 16:02:23 -0000 [thread overview]
Message-ID: <82a169eb513c54ef5ab49f4c78531752.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <CAHM4w1=aLOKY3PebMNb7cxWM_=n3TUJYB1WSvqrmMT6rQ+hRKg@mail.gmail.com>
hi Pratyush,
Most of the chages are translation level and architecture related. I was
able to get this working on Friday for 3 level tables on arm64. I am
trying to get this code back to you now.
Thanks,
Sameer
> HI Sameer,
>
>
> On Wed, Sep 9, 2015 at 4:02 AM, <sgoel@codeaurora.org> wrote:
>> Hi Pratush,
>> I added the mappings for PMD translations to the vtop function. This
>> helped in translating the address to physical. Issues seen:
>> 1. If PMD translates to a section. The physical translations does not
>> get
>> rid of the PMD flags. So, the physical address shows up as invalid and
>> code crashes when it tries to read this address from ELF.
>> 2. After treating this as a PTE table address, we see a compression of
>> around 50%.
>>
>
> Is it possible for you to share the modification you would have done
> on top of https://github.com/pratyushanand/makedumpfile.git:arm64_support.
> Actually, I have lost track of all the modifications you have done on
> top of my changes.
>
> I would like to review it closely this weekend and will suggest you
> whatever I find.
>
> ~Pratyush
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2015-09-14 16:02 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
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 [this message]
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=82a169eb513c54ef5ab49f4c78531752.squirrel@www.codeaurora.org \
--to=sgoel@codeaurora.org \
--cc=asamson@codeaurora.org \
--cc=ats-kumagai@wm.jp.nec.com \
--cc=kexec@lists.infradead.org \
--cc=panand@redhat.com \
--cc=pratyush.anand@gmail.com \
--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