From: Pratyush Anand <panand@redhat.com>
To: ats-kumagai@wm.jp.nec.com
Cc: Pratyush Anand <panand@redhat.com>,
sgoel@codeaurora.org, mansip@codeaurora.org,
asamson@codeaurora.org, kexec@lists.infradead.org
Subject: [PATCH Makedumpfile 00/10] arm64 cleanup and kaslr support
Date: Tue, 25 Oct 2016 12:52:52 +0530 [thread overview]
Message-ID: <cover.1477378297.git.panand@redhat.com> (raw)
These patches were lying in my tree for quite some time now. VMCOREINFO
numbers/symbols used in these patches have been made part of kdump kernel
patches for last few versions including v26. So, there seems no contention
on embedding VA_BITS, kimage_voffset and PHYS_OFFSET into vmcore.
These patches cleans up a lot arm64 code and also immunize it with many
kernel changes. Additionally,it adds 4 level 4K page support and support for
KASLR enabled kernel.
Azriel Samson (1):
arm64: Add support for 4level 4K page translations table
Pratyush Anand (9):
arm64: cleanup code, comment, blank space, blank lines etc
read_vmcoreinfo_long: Allow to read hex values as well
Introduce read_vmcoreinfo_ulong()
arm64: use already available PAGESIZE() and PAGESHIFT() macros
arm64: fix page_offset definition
arm64: fix re-filtering
arm64: use value of VA_BITS and PHYS_OFFSET embedded into vmcore
arm64: immunize identity mapped address finding w.r.t. kernel changes
arm64: fix memory layout as per changes in v4.6 kernel
arch/arm64.c | 245 ++++++++++++++++++++++-----------------------------------
makedumpfile.c | 46 +++++++++++
makedumpfile.h | 28 +++++--
3 files changed, 162 insertions(+), 157 deletions(-)
--
2.7.4
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2016-10-25 7:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 7:22 Pratyush Anand [this message]
2016-10-25 7:22 ` [PATCH Makedumpfile 01/10] arm64: cleanup code, comment, blank space, blank lines etc Pratyush Anand
2016-10-25 7:22 ` [PATCH Makedumpfile 02/10] read_vmcoreinfo_long: Allow to read hex values as well Pratyush Anand
2016-10-25 7:22 ` [PATCH Makedumpfile 03/10] Introduce read_vmcoreinfo_ulong() Pratyush Anand
2016-10-25 7:22 ` [PATCH Makedumpfile 04/10] arm64: use already available PAGESIZE() and PAGESHIFT() macros Pratyush Anand
2016-10-25 7:22 ` [PATCH Makedumpfile 05/10] arm64: fix page_offset definition Pratyush Anand
2016-10-25 7:22 ` [PATCH Makedumpfile 06/10] arm64: fix re-filtering Pratyush Anand
2016-10-25 7:22 ` [PATCH Makedumpfile 07/10] arm64: use value of VA_BITS and PHYS_OFFSET embedded into vmcore Pratyush Anand
2016-10-25 7:23 ` [PATCH Makedumpfile 08/10] arm64: immunize identity mapped address finding w.r.t. kernel changes Pratyush Anand
2016-10-25 7:23 ` [PATCH Makedumpfile 09/10] arm64: Add support for 4level 4K page translations table Pratyush Anand
2016-10-25 7:23 ` [PATCH Makedumpfile 10/10] arm64: fix memory layout as per changes in v4.6 kernel Pratyush Anand
2016-10-25 10:34 ` [PATCH Makedumpfile 00/10] arm64 cleanup and kaslr support Pratyush Anand
2016-11-01 9:11 ` Atsushi Kumagai
2016-11-15 6:34 ` Pratyush Anand
2016-11-15 11:18 ` Pratyush Anand
2016-11-16 5:44 ` Atsushi Kumagai
2016-11-16 8:33 ` Pratyush Anand
2016-11-16 8:40 ` Atsushi Kumagai
2016-11-17 4:36 ` Pratyush Anand
2016-12-08 0:18 ` Goel, Sameer
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=cover.1477378297.git.panand@redhat.com \
--to=panand@redhat.com \
--cc=asamson@codeaurora.org \
--cc=ats-kumagai@wm.jp.nec.com \
--cc=kexec@lists.infradead.org \
--cc=mansip@codeaurora.org \
--cc=sgoel@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