From: Thiago Jung Bauermann <bauerman@linux.vnet.ibm.com>
To: kexec@lists.infradead.org
Cc: Pratyush Anand <panand@redhat.com>,
geoff@infradead.org, catalin.marinas@arm.com,
will.deacon@arm.com, AKASHI Takahiro <takahiro.akashi@linaro.org>,
james.morse@arm.com, Mark Salter <msalter@redhat.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v21 1/8] arm64: kdump: reserve memory for crash dump kernel
Date: Wed, 06 Jul 2016 15:11:45 -0300 [thread overview]
Message-ID: <2543175.KeBui093Sr@hactar> (raw)
In-Reply-To: <20160706075226.27609-2-takahiro.akashi@linaro.org>
Am Mittwoch, 06 Juli 2016, 16:52:19 schrieb AKASHI Takahiro:
> On the startup of primary kernel, the memory region used by crash dump
> kernel must be specified by "crashkernel=" kernel parameter.
> reserve_crashkernel() will allocate and reserve the region for later use.
>
> User space tools, like kexec-tools, will be able to find that region
> marked as "Crash kernel" in /proc/iomem.
On powerpc, userspace tools get everything from the device tree (exposed to
userspace in /proc/device-tree/), not /proc/iomem.
In the case of the crashkernel reserved region, that information is in
/chosen/linux,crashkernel-base and /chosen/linux,crashkernel-size.
Either way is fine I think. I'm just mentioning this for reference in case
you want the ARM implementation to be closer to another arch which is also
based on the device tree.
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: bauerman@linux.vnet.ibm.com (Thiago Jung Bauermann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v21 1/8] arm64: kdump: reserve memory for crash dump kernel
Date: Wed, 06 Jul 2016 15:11:45 -0300 [thread overview]
Message-ID: <2543175.KeBui093Sr@hactar> (raw)
In-Reply-To: <20160706075226.27609-2-takahiro.akashi@linaro.org>
Am Mittwoch, 06 Juli 2016, 16:52:19 schrieb AKASHI Takahiro:
> On the startup of primary kernel, the memory region used by crash dump
> kernel must be specified by "crashkernel=" kernel parameter.
> reserve_crashkernel() will allocate and reserve the region for later use.
>
> User space tools, like kexec-tools, will be able to find that region
> marked as "Crash kernel" in /proc/iomem.
On powerpc, userspace tools get everything from the device tree (exposed to
userspace in /proc/device-tree/), not /proc/iomem.
In the case of the crashkernel reserved region, that information is in
/chosen/linux,crashkernel-base and /chosen/linux,crashkernel-size.
Either way is fine I think. I'm just mentioning this for reference in case
you want the ARM implementation to be closer to another arch which is also
based on the device tree.
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
next prev parent reply other threads:[~2016-07-06 18:12 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 7:52 [PATCH v21 0/8] arm64: kdump support AKASHI Takahiro
2016-07-06 7:52 ` AKASHI Takahiro
2016-07-06 7:52 ` [PATCH v21 1/8] arm64: kdump: reserve memory for crash dump kernel AKASHI Takahiro
2016-07-06 7:52 ` AKASHI Takahiro
2016-07-06 17:00 ` Geoff Levand
2016-07-06 17:00 ` Geoff Levand
2016-07-07 0:19 ` AKASHI Takahiro
2016-07-07 0:19 ` AKASHI Takahiro
2016-07-06 18:11 ` Thiago Jung Bauermann [this message]
2016-07-06 18:11 ` Thiago Jung Bauermann
2016-07-07 1:17 ` AKASHI Takahiro
2016-07-07 1:17 ` AKASHI Takahiro
2016-07-06 7:52 ` [PATCH v21 2/8] arm64: limit memory regions based on DT property, usable-memory AKASHI Takahiro
2016-07-06 7:52 ` AKASHI Takahiro
2016-07-06 17:48 ` Geoff Levand
2016-07-06 17:48 ` Geoff Levand
2016-07-06 7:52 ` [PATCH v21 3/8] arm64: kdump: implement machine_crash_shutdown() AKASHI Takahiro
2016-07-06 7:52 ` AKASHI Takahiro
2016-07-06 17:28 ` Geoff Levand
2016-07-06 17:28 ` Geoff Levand
2016-07-07 0:43 ` AKASHI Takahiro
2016-07-07 0:43 ` AKASHI Takahiro
2016-07-07 16:42 ` Geoff Levand
2016-07-07 16:42 ` Geoff Levand
2016-07-06 7:52 ` [PATCH v21 4/8] arm64: kdump: add kdump support AKASHI Takahiro
2016-07-06 7:52 ` AKASHI Takahiro
2016-07-06 17:38 ` Geoff Levand
2016-07-06 17:38 ` Geoff Levand
2016-07-07 0:49 ` AKASHI Takahiro
2016-07-07 0:49 ` AKASHI Takahiro
2016-07-06 7:52 ` [PATCH v21 5/8] arm64: kdump: add VMCOREINFO's for user-space coredump tools AKASHI Takahiro
2016-07-06 7:52 ` AKASHI Takahiro
2016-07-06 7:52 ` [PATCH v21 6/8] arm64: kdump: enable kdump in the arm64 defconfig AKASHI Takahiro
2016-07-06 7:52 ` AKASHI Takahiro
2016-07-06 7:52 ` [PATCH v21 7/8] arm64: kdump: update a kernel doc AKASHI Takahiro
2016-07-06 7:52 ` AKASHI Takahiro
2016-07-06 17:44 ` Geoff Levand
2016-07-06 17:44 ` Geoff Levand
2016-07-07 0:51 ` AKASHI Takahiro
2016-07-07 0:51 ` AKASHI Takahiro
2016-07-06 7:52 ` [PATCH v21 8/8] Documentation: dt: usable-memory and elfcorehdr nodes for arm64 kexec AKASHI Takahiro
2016-07-06 7:52 ` AKASHI Takahiro
2016-07-06 17:46 ` Geoff Levand
2016-07-06 17:46 ` Geoff Levand
2016-07-06 19:29 ` Thiago Jung Bauermann
2016-07-06 19:29 ` Thiago Jung Bauermann
2016-07-06 19:29 ` Thiago Jung Bauermann
2016-07-07 2:00 ` AKASHI Takahiro
2016-07-07 2:00 ` AKASHI Takahiro
2016-07-07 2:00 ` AKASHI Takahiro
2016-07-07 18:46 ` Thiago Jung Bauermann
2016-07-07 18:46 ` Thiago Jung Bauermann
2016-07-07 18:46 ` Thiago Jung Bauermann
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=2543175.KeBui093Sr@hactar \
--to=bauerman@linux.vnet.ibm.com \
--cc=catalin.marinas@arm.com \
--cc=geoff@infradead.org \
--cc=james.morse@arm.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=msalter@redhat.com \
--cc=panand@redhat.com \
--cc=takahiro.akashi@linaro.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.