Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pratyush Anand <panand@redhat.com>
To: AKASHI Takahiro <takahiro.akashi@linaro.org>, horms@verge.net.au
Cc: geoff@infradead.org, kexec@lists.infradead.org
Subject: Re: [PATCH v7 00/10] (kexec-tools) arm64: add kdump support
Date: Mon, 22 May 2017 11:52:25 +0530	[thread overview]
Message-ID: <089fe15a-ef8d-a325-59cb-f25ecf678deb@redhat.com> (raw)
In-Reply-To: <20170517055150.12601-1-takahiro.akashi@linaro.org>

Hi Akashi,

On Wednesday 17 May 2017 11:21 AM, AKASHI Takahiro wrote:
> My kernel patches of kdump support on arm64 were merged in v4.12-rc1.
>
> This patchset is synced with them and provides necessary changes for
> kexec-tools. It can be applied on top of kexec-tools master branch.
>
> Patch #1 to #4 are preparatory patches for succeeding patches,
> #5 to #9 are main part of kdump implementation for vmlinux support
> and #10 is for Image support.
>
> Changes for v7:
>  - rebased on the latest master
>  - fix incorrect return values on error (patch #4)
>  - implement get_crash_kernel_load_range() (patch #5)
>  - rename some variables/functions for better readability (patch #5/#9)
>  - add/revise comments
>


Thanks for the v7 updates. I tested this version as well, and it worked!!
Tested-by: Pratyush Anand <panand@redhat.com>


I will be sending v2 of D-cache enabling patches(for faster purgatory sha 
verification) once these patches are merged. If some one would like to test 
those patches in advance, it will be more than welcome. Patches lie in my 
github devel branch.

https://github.com/pratyushanand/kexec-tools.git : devel

~Pratyush

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

      parent reply	other threads:[~2017-05-22  6:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-17  5:51 [PATCH v7 00/10] (kexec-tools) arm64: add kdump support AKASHI Takahiro
2017-05-17  5:51 ` [PATCH v7 01/10] kexec: exntend the semantics of kexec_iomem_for_each_line AKASHI Takahiro
2017-05-17 23:37   ` David Woodhouse
2017-05-22  0:18     ` AKASHI Takahiro
2017-05-22 11:41       ` Simon Horman
2017-05-17  5:51 ` [PATCH v7 02/10] kexec: generalize and rename get_kernel_stext_sym() AKASHI Takahiro
2017-05-17  5:51 ` [PATCH v7 03/10] arm64: identify PHYS_OFFSET correctly AKASHI Takahiro
2017-05-17  5:51 ` [PATCH v7 04/10] arm64: change return values on error to negative AKASHI Takahiro
2017-05-17  5:51 ` [PATCH v7 05/10] arm64: kdump: identify memory regions AKASHI Takahiro
2017-05-17  5:51 ` [PATCH v7 06/10] arm64: kdump: add elf core header segment AKASHI Takahiro
2017-05-17  5:51 ` [PATCH v7 07/10] arm64: kdump: set up kernel image segment AKASHI Takahiro
2017-05-17  5:51 ` [PATCH v7 08/10] arm64: kdump: set up other segments AKASHI Takahiro
2017-05-17  5:51 ` [PATCH v7 09/10] arm64: kdump: add DT properties to crash dump kernel's dtb AKASHI Takahiro
2017-05-17  5:51 ` [PATCH v7 10/10] arm64: kdump: Add support for binary image files AKASHI Takahiro
2017-05-22  6:22 ` Pratyush Anand [this message]

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=089fe15a-ef8d-a325-59cb-f25ecf678deb@redhat.com \
    --to=panand@redhat.com \
    --cc=geoff@infradead.org \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=takahiro.akashi@linaro.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