All of lore.kernel.org
 help / color / mirror / Atom feed
From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: Pratyush Anand <panand@redhat.com>
Cc: geoff@infradead.org, horms@verge.net.au, kexec@lists.infradead.org
Subject: Re: [PATCH v6 0/9] (kexec-tools) arm64: add kdump support
Date: Fri, 12 May 2017 15:25:09 +0900	[thread overview]
Message-ID: <20170512062508.GA28830@linaro.org> (raw)
In-Reply-To: <147ae0e7-ebe9-e762-2c36-d4b88d4dc395@redhat.com>

On Fri, May 12, 2017 at 08:21:07AM +0530, Pratyush Anand wrote:
> On Wednesday 15 March 2017 03:08 PM, AKASHI Takahiro wrote:
> >My kernel patches of kdump support on arm64 are currently under review.
> >
> >This patchset is synced with them (v33 [1]) and provides necessary changes
> >for kexec-tools. It can be applied on top of kexec-tools master branch.
> >
> >[1] T.B.D.
> >
> >Changes for v6:
> > - use get_kernel_sym() from x86, not from arm (patch #2)
> > - always take root node's "#address-cells" and "#size-cells" into account
> >   when adding "linux,usable-memory-range" and "linux,elfcorehdr"
> >   (patch #8)
> 
> 
> I think these patches can be merged now, as kernel patches are there in upstream.

Yeah, but I might want to make _cosmetic_ changes/clean-up stuff
as I'm now working on kexec_file_load() support and want to minimize
the gap between the kernel code and kexec-tools.

I'll let all of you know once I've done. Hopefully early next week.
So if anybody have comments, those will be very much appreciated.

Thanks,
-Takahiro AKASHI

> 
> For the series:
> 
> Tested-by: Pratyush Anand <panand@redhat.com>
> Reviewed-by: Pratyush Anand <panand@redhat.com>
> 
> >
> >Changes for v5:
> > - remove "linux,crashkernel-base/size" handling aligned with a change
> >   on the kernel side
> >
> >Changes for v4:
> > - rebased on the master branch (including Geoff's v6)
> > - revive "linux,usable-memory-range" DT property (from v2), dropping
> >   use of "reserved-memory" nodes introduced in v3 (patch #8)
> > - extend the semantics of kexec_iomem_for_each_line() per Pratyush
> >   (patch #1)
> >
> >Changes for v3:
> > - rebased on Geoff's v5
> > - fix a value of estimated PHYS_OFFSET
> > - add a kernel code/data segment because they now reside out of linear
> >   mapping due to KASLR introduction
> > - remove "linux,usable-memory-range" dependency, instead using
> >   "reserved-memory" node
> > - add -mem-min/-mem-max support
> >
> >Changes for v2:
> > - trim a temoprary buffer in setup_2nd_dtb()
> > - add patch#6("kexec: generalize and rename get_kernel_stext_sym()")
> > - update patch#7 from Pratyush
> >   (re-worked by akashi)
> >
> >AKASHI Takahiro (7):
> >  kexec: exntend the semantics of kexec_iomem_for_each_line
> >  arm64: identify PHYS_OFFSET correctly
> >  arm64: kdump: identify memory regions
> >  arm64: kdump: add elf core header segment
> >  arm64: kdump: set up kernel image segment
> >  arm64: kdump: set up other segments
> >  arm64: kdump: add DT properties to crash dump kernel's dtb
> >
> >Pratyush Anand (2):
> >  kexec: generalize and rename get_kernel_stext_sym()
> >  arm64: kdump: Add support for binary image files
> >
> > kexec/Makefile                       |   1 +
> > kexec/arch/arm/crashdump-arm.c       |  40 +-----
> > kexec/arch/arm64/Makefile            |   2 +
> > kexec/arch/arm64/crashdump-arm64.c   | 219 +++++++++++++++++++++++++++++++-
> > kexec/arch/arm64/crashdump-arm64.h   |  18 ++-
> > kexec/arch/arm64/iomem.h             |  10 ++
> > kexec/arch/arm64/kexec-arm64.c       | 239 +++++++++++++++++++++++++++++++++--
> > kexec/arch/arm64/kexec-elf-arm64.c   |  25 +++-
> > kexec/arch/arm64/kexec-image-arm64.c |  12 ++
> > kexec/arch/i386/crashdump-x86.c      |  29 -----
> > kexec/kexec-iomem.c                  |  15 ++-
> > kexec/kexec.h                        |   2 +
> > kexec/symbols.c                      |  34 +++++
> > 13 files changed, 551 insertions(+), 95 deletions(-)
> > create mode 100644 kexec/arch/arm64/iomem.h
> > create mode 100644 kexec/symbols.c
> >

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

      reply	other threads:[~2017-05-12  6:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-15  9:38 [PATCH v6 0/9] (kexec-tools) arm64: add kdump support AKASHI Takahiro
2017-03-15  9:38 ` [PATCH v6 1/9] kexec: exntend the semantics of kexec_iomem_for_each_line AKASHI Takahiro
2017-03-15  9:38 ` [PATCH v6 2/9] kexec: generalize and rename get_kernel_stext_sym() AKASHI Takahiro
2017-03-15  9:38 ` [PATCH v6 3/9] arm64: identify PHYS_OFFSET correctly AKASHI Takahiro
2017-03-15  9:38 ` [PATCH v6 4/9] arm64: kdump: identify memory regions AKASHI Takahiro
2017-03-15  9:38 ` [PATCH v6 5/9] arm64: kdump: add elf core header segment AKASHI Takahiro
2017-03-15  9:38 ` [PATCH v6 6/9] arm64: kdump: set up kernel image segment AKASHI Takahiro
2017-03-15  9:38 ` [PATCH v6 7/9] arm64: kdump: set up other segments AKASHI Takahiro
2017-03-15  9:38 ` [PATCH v6 8/9] arm64: kdump: add DT properties to crash dump kernel's dtb AKASHI Takahiro
2017-03-15  9:38 ` [PATCH v6 9/9] arm64: kdump: Add support for binary image files AKASHI Takahiro
2017-05-12  2:51 ` [PATCH v6 0/9] (kexec-tools) arm64: add kdump support Pratyush Anand
2017-05-12  6:25   ` AKASHI Takahiro [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=20170512062508.GA28830@linaro.org \
    --to=takahiro.akashi@linaro.org \
    --cc=geoff@infradead.org \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=panand@redhat.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.