From: takahiro.akashi@linaro.org (AKASHI Takahiro) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v26 0/7] arm64: add kdump support Date: Tue, 18 Oct 2016 15:26:19 +0900 [thread overview] Message-ID: <20161018062617.GN19531@linaro.org> (raw) In-Reply-To: <3400bddc-9c6e-b69a-b57d-62921197bef9@cisco.com> Ruslan, On Mon, Oct 17, 2016 at 06:41:01PM +0300, Ruslan Bilovol wrote: > Hi, > > On 09/07/2016 07:29 AM, AKASHI Takahiro wrote: > > v26-specific note: After a comment from Rob[0], an idea of adding > > "linux,usable-memory-range" was dropped. Instead, an existing > > "reserved-memory" node will be used to limit usable memory ranges > > on crash dump kernel. > > This works not only on UEFI/ACPI systems but also on DT-only systems, > > but if he really insists on using DT-specific "usable-memory" property, > > I will post additional patches for kexec-tools. Those would be > > redundant, though. > > Even in that case, the kernel will not have to be changed. > > > >This patch series adds kdump support on arm64. > >There are some prerequisite patches [1],[2]. > > > >To load a crash-dump kernel to the systems, a series of patches to > >kexec-tools, which have not yet been merged upstream, are needed. > >Please always use my latest kdump patches, v3 [3]. > > > >To examine vmcore (/proc/vmcore) on a crash-dump kernel, you can use > > - crash utility (coming v7.1.6 or later) [4] > > (Necessary patches have already been queued in the master.) > > > > > >[0] http://lists.infradead.org/pipermail/linux-arm-kernel/2016-August/452582.html > >[1] "arm64: mark reserved memblock regions explicitly in iomem" > > http://lists.infradead.org/pipermail/linux-arm-kernel/2016-August/450433.html > >[2] "efi: arm64: treat regions with WT/WC set but WB cleared as memory" > > http://lists.infradead.org/pipermail/linux-arm-kernel/2016-August/451491.html > >[3] T.B.D. > >[4] https://github.com/crash-utility/crash.git > > Are you going to rebase your patch series onto v4.9-rc1 tag soon? I see Yes, definitely as soon as possible! (actually I've done it.) But before submitting a new version, I need to convince Rob (Herring) that he would accept my old approach (v25) regarding specifying usable memory for crash dump kernel: http://lists.infradead.org/pipermail/linux-arm-kernel/2016-September/459379.html > that patches [1] and [2] are already in v4.9-rc1, but when tried to apply > this series, I've got conflict on first patch of the series ("arm64: kdump: > reserve memory for crash dump kernel"). I want to try arm64 kdump > patches again on my board, so I'm interested in this. The question is > whether I need to rebase it myself or you will do the same (and address > comments) soon. Thank you for your interests and sorry for any inconvenience. -Takahiro AKASHI > Also I see Geoff published v6 of arm64 kexec-tools patches, so same > question is applicable to "(kexec-tools) arm64: add kdump support" > patch series. > > Thanks, > Ruslan >
WARNING: multiple messages have this Message-ID (diff)
From: AKASHI Takahiro <takahiro.akashi@linaro.org> To: Ruslan Bilovol <rbilovol@cisco.com> 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 v26 0/7] arm64: add kdump support Date: Tue, 18 Oct 2016 15:26:19 +0900 [thread overview] Message-ID: <20161018062617.GN19531@linaro.org> (raw) In-Reply-To: <3400bddc-9c6e-b69a-b57d-62921197bef9@cisco.com> Ruslan, On Mon, Oct 17, 2016 at 06:41:01PM +0300, Ruslan Bilovol wrote: > Hi, > > On 09/07/2016 07:29 AM, AKASHI Takahiro wrote: > > v26-specific note: After a comment from Rob[0], an idea of adding > > "linux,usable-memory-range" was dropped. Instead, an existing > > "reserved-memory" node will be used to limit usable memory ranges > > on crash dump kernel. > > This works not only on UEFI/ACPI systems but also on DT-only systems, > > but if he really insists on using DT-specific "usable-memory" property, > > I will post additional patches for kexec-tools. Those would be > > redundant, though. > > Even in that case, the kernel will not have to be changed. > > > >This patch series adds kdump support on arm64. > >There are some prerequisite patches [1],[2]. > > > >To load a crash-dump kernel to the systems, a series of patches to > >kexec-tools, which have not yet been merged upstream, are needed. > >Please always use my latest kdump patches, v3 [3]. > > > >To examine vmcore (/proc/vmcore) on a crash-dump kernel, you can use > > - crash utility (coming v7.1.6 or later) [4] > > (Necessary patches have already been queued in the master.) > > > > > >[0] http://lists.infradead.org/pipermail/linux-arm-kernel/2016-August/452582.html > >[1] "arm64: mark reserved memblock regions explicitly in iomem" > > http://lists.infradead.org/pipermail/linux-arm-kernel/2016-August/450433.html > >[2] "efi: arm64: treat regions with WT/WC set but WB cleared as memory" > > http://lists.infradead.org/pipermail/linux-arm-kernel/2016-August/451491.html > >[3] T.B.D. > >[4] https://github.com/crash-utility/crash.git > > Are you going to rebase your patch series onto v4.9-rc1 tag soon? I see Yes, definitely as soon as possible! (actually I've done it.) But before submitting a new version, I need to convince Rob (Herring) that he would accept my old approach (v25) regarding specifying usable memory for crash dump kernel: http://lists.infradead.org/pipermail/linux-arm-kernel/2016-September/459379.html > that patches [1] and [2] are already in v4.9-rc1, but when tried to apply > this series, I've got conflict on first patch of the series ("arm64: kdump: > reserve memory for crash dump kernel"). I want to try arm64 kdump > patches again on my board, so I'm interested in this. The question is > whether I need to rebase it myself or you will do the same (and address > comments) soon. Thank you for your interests and sorry for any inconvenience. -Takahiro AKASHI > Also I see Geoff published v6 of arm64 kexec-tools patches, so same > question is applicable to "(kexec-tools) arm64: add kdump support" > patch series. > > Thanks, > Ruslan > _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2016-10-18 6:26 UTC|newest] Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-09-07 4:29 [PATCH v26 0/7] arm64: add kdump support AKASHI Takahiro 2016-09-07 4:29 ` AKASHI Takahiro 2016-09-07 4:29 ` [PATCH v26 1/7] arm64: kdump: reserve memory for crash dump kernel AKASHI Takahiro 2016-09-07 4:29 ` AKASHI Takahiro 2016-09-22 10:23 ` Matthias Bruger 2016-09-22 10:23 ` Matthias Bruger 2016-09-23 8:37 ` AKASHI Takahiro 2016-09-23 8:37 ` AKASHI Takahiro 2016-09-07 4:29 ` [PATCH v26 2/7] arm64: kdump: implement machine_crash_shutdown() AKASHI Takahiro 2016-09-07 4:29 ` AKASHI Takahiro 2016-09-14 18:09 ` James Morse 2016-09-14 18:09 ` James Morse 2016-09-15 8:13 ` Marc Zyngier 2016-09-15 8:13 ` Marc Zyngier 2016-09-16 3:21 ` AKASHI Takahiro 2016-09-16 3:21 ` AKASHI Takahiro 2016-09-16 14:49 ` James Morse 2016-09-16 14:49 ` James Morse 2016-09-20 7:36 ` AKASHI Takahiro 2016-09-20 7:36 ` AKASHI Takahiro 2016-09-07 4:29 ` [PATCH v26 3/7] arm64: kdump: add kdump support AKASHI Takahiro 2016-09-07 4:29 ` AKASHI Takahiro 2016-09-16 14:50 ` James Morse 2016-09-16 14:50 ` James Morse 2016-09-20 7:46 ` AKASHI Takahiro 2016-09-20 7:46 ` AKASHI Takahiro 2016-09-22 15:50 ` Matthias Brugger 2016-09-22 15:50 ` Matthias Brugger 2016-09-07 4:29 ` [PATCH v26 4/7] arm64: kdump: add VMCOREINFO's for user-space coredump tools AKASHI Takahiro 2016-09-07 4:29 ` AKASHI Takahiro 2016-09-16 16:04 ` James Morse 2016-09-16 16:04 ` James Morse 2016-09-07 4:29 ` [PATCH v26 5/7] arm64: kdump: enable kdump in the arm64 defconfig AKASHI Takahiro 2016-09-07 4:29 ` AKASHI Takahiro 2016-09-07 4:29 ` [PATCH v26 6/7] arm64: kdump: update a kernel doc AKASHI Takahiro 2016-09-07 4:29 ` AKASHI Takahiro 2016-09-16 16:08 ` James Morse 2016-09-16 16:08 ` James Morse 2016-09-20 8:27 ` AKASHI Takahiro 2016-09-20 8:27 ` AKASHI Takahiro 2016-09-26 17:21 ` Matthias Brugger 2016-09-26 17:21 ` Matthias Brugger [not found] ` <20160907042908.6232-1-takahiro.akashi-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> 2016-09-07 4:32 ` [PATCH v26 7/7] Documentation: dt: chosen properties for arm64 kdump AKASHI Takahiro 2016-09-07 4:32 ` AKASHI Takahiro 2016-09-07 4:32 ` AKASHI Takahiro [not found] ` <20160907043203.6309-1-takahiro.akashi-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> 2016-09-16 13:03 ` Rob Herring 2016-09-16 13:03 ` Rob Herring 2016-09-16 13:03 ` Rob Herring 2016-09-07 4:37 ` [PATCH v26 0/7] arm64: add kdump support AKASHI Takahiro 2016-09-07 4:37 ` AKASHI Takahiro 2016-09-16 16:04 ` James Morse 2016-09-16 16:04 ` James Morse 2016-09-16 20:17 ` Ard Biesheuvel 2016-09-16 20:17 ` Ard Biesheuvel 2016-09-19 16:05 ` James Morse 2016-09-19 16:05 ` James Morse 2016-09-19 16:10 ` Ard Biesheuvel 2016-09-19 16:10 ` Ard Biesheuvel 2016-09-21 7:42 ` AKASHI Takahiro 2016-09-21 7:42 ` AKASHI Takahiro 2016-09-21 7:33 ` AKASHI Takahiro 2016-09-21 7:33 ` AKASHI Takahiro 2016-10-03 7:54 ` Manish Jaggi 2016-10-03 7:54 ` Manish Jaggi 2016-10-03 11:04 ` AKASHI Takahiro 2016-10-03 11:04 ` AKASHI Takahiro 2016-10-03 12:41 ` Manish Jaggi 2016-10-03 12:41 ` Manish Jaggi 2016-10-04 2:56 ` AKASHI Takahiro 2016-10-04 2:56 ` AKASHI Takahiro 2016-10-04 9:46 ` James Morse 2016-10-04 9:46 ` James Morse 2016-10-04 10:05 ` Manish Jaggi 2016-10-04 10:05 ` Manish Jaggi 2016-10-04 10:53 ` James Morse 2016-10-04 10:53 ` James Morse 2016-10-04 13:23 ` Manish Jaggi 2016-10-04 13:23 ` Manish Jaggi 2016-10-05 5:48 ` AKASHI Takahiro 2016-10-05 5:48 ` AKASHI Takahiro 2016-10-05 5:41 ` AKASHI Takahiro 2016-10-05 5:41 ` AKASHI Takahiro 2016-10-04 10:18 ` Mark Rutland 2016-10-04 10:18 ` Mark Rutland 2016-10-17 15:41 ` Ruslan Bilovol 2016-10-17 15:41 ` Ruslan Bilovol 2016-10-18 6:26 ` AKASHI Takahiro [this message] 2016-10-18 6:26 ` AKASHI Takahiro 2016-11-01 12:19 ` Ruslan Bilovol 2016-11-01 12:19 ` Ruslan Bilovol
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=20161018062617.GN19531@linaro.org \ --to=takahiro.akashi@linaro.org \ --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: linkBe 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.