Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Chen Zhou <chenzhou10@huawei.com>
Cc: kexec@lists.infradead.org
Subject: Re: [PATCH v3] arm64: kdump: add another DT property to crash dump kernel's dtb
Date: Sat, 6 Jun 2020 15:19:33 +0200	[thread overview]
Message-ID: <20200606131933.GA24391@vergenet.net> (raw)
In-Reply-To: <20200521083257.53415-1-chenzhou10@huawei.com>

On Thu, May 21, 2020 at 04:32:57PM +0800, Chen Zhou wrote:
> Currently, there is only one crash kernel region on arm64, we add
> another region "crash kernel low" used for crash dump kernel devices.
> 
> To do this, we add DT property "linux,low-memory-range" to crash
> dump kernel's dtb to pass the low region.
> 
> Signed-off-by: Chen Zhou <chenzhou10@huawei.com>
> ---
> For "support reserving crashkernel above 4G on arm64 kdump", we need
> to modify the kexec-tools.
> 
> Changes since [v2]:
> - Rebase to latest kexec-tools code.
> 
> Changes since [v1]:
> - Add another DT property "linux,low-memory-range" to crash dump kernel's
> dtb to pass the low region instead of reusing "linux,usable-memory-range".
> 
> [1]: http://lists.infradead.org/pipermail/kexec/2019-April/022792.html
> [2]: http://lists.infradead.org/pipermail/kexec/2019-August/023569.html

Thanks.

I think it would be appropriate for me to apply this change to
kexec-tools once the corresponding changes have been accepted to
the kernel.

Please repost when that is the case.

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

  reply	other threads:[~2020-06-06 13:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-21  8:32 [PATCH v3] arm64: kdump: add another DT property to crash dump kernel's dtb Chen Zhou
2020-06-06 13:19 ` Simon Horman [this message]
2020-06-06 13:33   ` chenzhou

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=20200606131933.GA24391@vergenet.net \
    --to=horms@verge.net.au \
    --cc=chenzhou10@huawei.com \
    --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