From: yanjiang.jin@windriver.com (yanjiang.jin at windriver.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] kdump test comments:
Date: Tue, 2 May 2017 17:47:17 +0800 [thread overview]
Message-ID: <20170502094718.188172-1-yanjiang.jin@windriver.com> (raw)
From: Yanjiang Jin <yanjiang.jin@windriver.com>
1. Execute a kdump test on a "Freescale LayerScape LS1021E, Version: 2.0 board";
2. I think may all "proc-v7-3level" CPUs need this patch, but I only validated it on LS1021, so still use
#ifdef CONFIG_SOC_LS1021A
to wrap this change;
3. Append "crashkernel=128M at 2560M" in UBoot's command line;
4. Use uImage as kdump's first kernel and capture kernel, but ls1021A doesn't define LOADADDR now,
so add below code in "arch/arm/boot/Makefile" temporarily to build an uImage:
+ifeq ($(CONFIG_SOC_LS1021A), y)
+LOADADDR=0x80008000
+endif
+
Yanjiang Jin (1):
arm: proc-v7-3level.S: SOC_LS1021A: clear TTBCR.T1SZ
arch/arm/mm/proc-v7-3level.S | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
--
1.9.1
next reply other threads:[~2017-05-02 9:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 9:47 yanjiang.jin at windriver.com [this message]
2017-05-02 9:47 ` [PATCH] arm: proc-v7-3level.S: SOC_LS1021A: clear TTBCR.T1SZ yanjiang.jin at windriver.com
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=20170502094718.188172-1-yanjiang.jin@windriver.com \
--to=yanjiang.jin@windriver.com \
--cc=linux-arm-kernel@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