public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
From: Mika Westerberg <ext-mika.1.westerberg@nokia.com>
To: igawa@mxs.nes.nec.co.jp
Cc: kexec@lists.infradead.org,
	Mika Westerberg <ext-mika.1.westerberg@nokia.com>
Subject: [PATCH v2 0/2] makedumpfile: few ARM fixes
Date: Mon,  8 Nov 2010 09:59:26 +0200	[thread overview]
Message-ID: <cover.1289202688.git.ext-mika.1.westerberg@nokia.com> (raw)

Hi,

While using makedumpfile on ARM I found few issues from the current
implementation. Basically the current implementation only works on
3G/1G VM split but not others.

These patches should make makedumpfile on ARM to work on other VM
split values as well. I've tested with 1G/3G, 2G/2G, 3G/1G, and
VMSPLIT_3G_OPT (2.7G/1.3G).

Changes to previous version:
	- removed any references to vmalloc_start as per review comments

This version still allows users to use '--vtop' option to perform V->P
translations via page tables.

Regards,
MW

Mika Westerberg (2):
  ARM: determine PAGE_OFFSET from _stext
  ARM: don't depend on vmalloc_start

 arm.c          |   50 +++++++++-----------------------------------------
 makedumpfile.h |    1 -
 2 files changed, 9 insertions(+), 42 deletions(-)


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

             reply	other threads:[~2010-11-08  8:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-08  7:59 Mika Westerberg [this message]
2010-11-08  7:59 ` [PATCH v2 1/2] ARM: determine PAGE_OFFSET from _stext Mika Westerberg
2010-11-08  7:59 ` [PATCH v2 2/2] ARM: don't depend on vmalloc_start Mika Westerberg
2010-11-09  2:51 ` [PATCH v2 0/2] makedumpfile: few ARM fixes Masayuki Igawa

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.1289202688.git.ext-mika.1.westerberg@nokia.com \
    --to=ext-mika.1.westerberg@nokia.com \
    --cc=igawa@mxs.nes.nec.co.jp \
    --cc=kexec@lists.infradead.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