All of lore.kernel.org
 help / color / mirror / Atom feed
From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: "Goel, Sameer" <sgoel@codeaurora.org>
Cc: mark.rutland@arm.com, geoff@infradead.org,
	catalin.marinas@arm.com, will.deacon@arm.com,
	james.morse@arm.com, bauerman@linux.vnet.ibm.com,
	dyoung@redhat.com, kexec@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v32 00/13] arm64: add kdump support
Date: Thu, 2 Mar 2017 19:34:08 +0900	[thread overview]
Message-ID: <20170302103407.GC1746@linaro.org> (raw)
In-Reply-To: <1f4c1497-129d-7350-89c1-1ba0a6764ba5@codeaurora.org>

On Wed, Mar 01, 2017 at 05:51:21PM -0700, Goel, Sameer wrote:
> 
> 
> On 2/7/2017 1:06 AM, AKASHI Takahiro wrote:
> > This patch series adds kdump support on arm64.
> > 
> > To load a crash-dump kernel to the systems, a series of patches to
> > kexec-tools[1] are also needed. Please use the latest one, v5 [2].
> > For your convinience, you can pick them up from:
> >    https://git.linaro.org/people/takahiro.akashi/linux-aarch64.git arm64/kdump
> >    https://git.linaro.org/people/takahiro.akashi/kexec-tools.git arm64/kdump
> > 
> > To examine vmcore (/proc/vmcore) on a crash-dump kernel, you can use
> >   - crash utility (v7.1.8 or later, i.e. master for now) [3]
> > 
> > I tested this patchset on fast model and hikey.
> > (under various configurations, in particular 4KB-page/39,48-bits, 64KB-page/42
> > -bits with hibernate)
> > 
> > The previous versions were also:
> > Tested-by: Pratyush Anand <panand@redhat.com> (v29, mustang and seattle)
> > Tested-by: James Morse <james.morse@arm.com> (v27, Juno)
> > 
> I tested this patch set on a QDT2400 device with 4k 4-level setup. This patchset worked after applying [1].

Thank you for your test and report.
While adding [1] is yet to be discussed, I will post v33 as soon as
possible after v4.10-rc1.

Thanks,
-Takahiro AKASHI


> [1] [PATCH] efi/libstub/arm*: Set default address and size cells values for an empty dtb
> 
> Without the above patch the start address of the crash kernel is recorded incorrectly and the 
> memblock_cap_memory_range clears out the incorrect range. 
>  
> Thanks,
> Sameer
> -- 
> Qualcomm Datacenter Technologies as an affiliate of Qualcomm Technologies, Inc.
> Qualcomm Technologies, Inc. is a member of the
> Code Aurora Forum, a Linux Foundation Collaborative Project.

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

WARNING: multiple messages have this Message-ID (diff)
From: takahiro.akashi@linaro.org (AKASHI Takahiro)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v32 00/13] arm64: add kdump support
Date: Thu, 2 Mar 2017 19:34:08 +0900	[thread overview]
Message-ID: <20170302103407.GC1746@linaro.org> (raw)
In-Reply-To: <1f4c1497-129d-7350-89c1-1ba0a6764ba5@codeaurora.org>

On Wed, Mar 01, 2017 at 05:51:21PM -0700, Goel, Sameer wrote:
> 
> 
> On 2/7/2017 1:06 AM, AKASHI Takahiro wrote:
> > This patch series adds kdump support on arm64.
> > 
> > To load a crash-dump kernel to the systems, a series of patches to
> > kexec-tools[1] are also needed. Please use the latest one, v5 [2].
> > For your convinience, you can pick them up from:
> >    https://git.linaro.org/people/takahiro.akashi/linux-aarch64.git arm64/kdump
> >    https://git.linaro.org/people/takahiro.akashi/kexec-tools.git arm64/kdump
> > 
> > To examine vmcore (/proc/vmcore) on a crash-dump kernel, you can use
> >   - crash utility (v7.1.8 or later, i.e. master for now) [3]
> > 
> > I tested this patchset on fast model and hikey.
> > (under various configurations, in particular 4KB-page/39,48-bits, 64KB-page/42
> > -bits with hibernate)
> > 
> > The previous versions were also:
> > Tested-by: Pratyush Anand <panand@redhat.com> (v29, mustang and seattle)
> > Tested-by: James Morse <james.morse@arm.com> (v27, Juno)
> > 
> I tested this patch set on a QDT2400 device with 4k 4-level setup. This patchset worked after applying [1].

Thank you for your test and report.
While adding [1] is yet to be discussed, I will post v33 as soon as
possible after v4.10-rc1.

Thanks,
-Takahiro AKASHI


> [1] [PATCH] efi/libstub/arm*: Set default address and size cells values for an empty dtb
> 
> Without the above patch the start address of the crash kernel is recorded incorrectly and the 
> memblock_cap_memory_range clears out the incorrect range. 
>  
> Thanks,
> Sameer
> -- 
> Qualcomm Datacenter Technologies as an affiliate of Qualcomm Technologies, Inc.
> Qualcomm Technologies, Inc. is a member of the
> Code Aurora Forum, a Linux Foundation Collaborative Project.

  reply	other threads:[~2017-03-02 10:32 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-07  8:06 [PATCH v32 00/13] arm64: add kdump support AKASHI Takahiro
2017-02-07  8:06 ` AKASHI Takahiro
2017-02-07  8:08 ` [PATCH v32 01/13] memblock: add memblock_clear_nomap() AKASHI Takahiro
2017-02-07  8:08   ` AKASHI Takahiro
2017-02-07  8:08   ` AKASHI Takahiro
2017-02-07  8:08 ` [PATCH v32 02/13] memblock: add memblock_cap_memory_range() AKASHI Takahiro
2017-02-07  8:08   ` AKASHI Takahiro
2017-02-07  8:08   ` AKASHI Takahiro
2017-02-07  8:08 ` [PATCH v32 03/13] arm64: limit memory regions based on DT property, usable-memory-range AKASHI Takahiro
2017-02-07  8:08   ` AKASHI Takahiro
2017-02-07  8:08 ` [PATCH v32 04/13] arm64: kdump: reserve memory for crash dump kernel AKASHI Takahiro
2017-02-07  8:08   ` AKASHI Takahiro
2017-02-07  8:08 ` [PATCH v32 05/13] arm64: mm: allow for unmapping part of kernel mapping AKASHI Takahiro
2017-02-07  8:08   ` AKASHI Takahiro
2017-02-07  8:08 ` [PATCH v32 06/13] arm64: kdump: protect crash dump kernel memory AKASHI Takahiro
2017-02-07  8:08   ` AKASHI Takahiro
2017-02-17 16:08   ` James Morse
2017-02-17 16:08     ` James Morse
2017-02-07  8:08 ` [PATCH v32 07/13] arm64: hibernate: preserve kdump image around hibernation AKASHI Takahiro
2017-02-07  8:08   ` AKASHI Takahiro
2017-02-15 12:12   ` James Morse
2017-02-15 12:12     ` James Morse
2017-02-16  9:52     ` AKASHI Takahiro
2017-02-16  9:52       ` AKASHI Takahiro
2017-02-07  8:09 ` [PATCH v32 08/13] arm64: kdump: implement machine_crash_shutdown() AKASHI Takahiro
2017-02-07  8:09   ` AKASHI Takahiro
2017-02-07  8:09 ` [PATCH v32 09/13] arm64: kdump: add VMCOREINFO's for user-space tools AKASHI Takahiro
2017-02-07  8:09   ` AKASHI Takahiro
2017-02-07  8:09 ` [PATCH v32 10/13] arm64: kdump: provide /proc/vmcore file AKASHI Takahiro
2017-02-07  8:09   ` AKASHI Takahiro
2017-02-07  8:09 ` [PATCH v32 11/13] arm64: kdump: enable kdump in defconfig AKASHI Takahiro
2017-02-07  8:09   ` AKASHI Takahiro
2017-02-07  8:09 ` [PATCH v32 12/13] Documentation: kdump: describe arm64 port AKASHI Takahiro
2017-02-07  8:09   ` AKASHI Takahiro
2017-02-07  8:10 ` [PATCH v32 13/13] Documentation: dt: chosen properties for arm64 kdump AKASHI Takahiro
2017-02-07  8:10   ` AKASHI Takahiro
2017-02-07  8:10   ` AKASHI Takahiro
2017-02-08  5:39 ` [PATCH v32 00/13] arm64: add kdump support Pratyush Anand
2017-02-08  5:39   ` Pratyush Anand
2017-03-02  0:51 ` Goel, Sameer
2017-03-02  0:51   ` Goel, Sameer
2017-03-02 10:34   ` AKASHI Takahiro [this message]
2017-03-02 10:34     ` AKASHI Takahiro

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=20170302103407.GC1746@linaro.org \
    --to=takahiro.akashi@linaro.org \
    --cc=bauerman@linux.vnet.ibm.com \
    --cc=catalin.marinas@arm.com \
    --cc=dyoung@redhat.com \
    --cc=geoff@infradead.org \
    --cc=james.morse@arm.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=sgoel@codeaurora.org \
    --cc=will.deacon@arm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.