From: Hari Bathini <hbathini@linux.vnet.ibm.com>
To: Kexec-ml <kexec@lists.infradead.org>,
Tachibana-san <tachibana@mxm.nes.nec.co.jp>,
Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>,
Ken'ichi <oomichi@mxs.nes.nec.co.jp>
Subject: [PATCH v2 0/2] PPC64: Add virtual to physical address translation support for vmalloc region
Date: Mon, 28 Jul 2014 19:43:31 +0530 [thread overview]
Message-ID: <20140728141253.3399.4397.stgit@localhost.localdomain> (raw)
In makedumpfile tool, currently there is no support for virtual to physical
address translation of vmalloc region on PPC64 architecture. These patches
add this support. The patches have been tested by erasing data in vmalloc
region, verfying for eraseinfo in the resultant ELF dump and verifiying the
resultant ELF dump for sanity using crash utility. Also, tested the patches
successfully with eppic scripts.
Changes in v2:
1. Allocating memory to read page tables only when vmalloc address
translation is requested.
2. Fixed coding style issues.
---
Hari Bathini (2):
makedumpfile: Initialize for vmalloc address translation support in PPC64 arch
makedumpfile: vtop address translation support for vmalloc region in PPC64 arch
arch/ppc64.c | 172 ++++++++++++++++++++++++++++++++++++++++++++++++++++----
makedumpfile.c | 7 ++
makedumpfile.h | 82 ++++++++++++++++++++++++++-
3 files changed, 248 insertions(+), 13 deletions(-)
--
- Hari
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2014-07-28 14:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 14:13 Hari Bathini [this message]
2014-07-28 14:13 ` [PATCH v2 1/2] makedumpfile: Initialize for vmalloc address translation support in PPC64 arch Hari Bathini
2014-07-28 14:13 ` [PATCH v2 2/2] makedumpfile: vtop address translation support for vmalloc region " Hari Bathini
2014-08-06 23:50 ` Atsushi Kumagai
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=20140728141253.3399.4397.stgit@localhost.localdomain \
--to=hbathini@linux.vnet.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
--cc=oomichi@mxs.nes.nec.co.jp \
--cc=tachibana@mxm.nes.nec.co.jp \
/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