From: Linus Walleij <linus.walleij@linaro.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: "Russell King" <linux@armlinux.org.uk>,
"Ard Biesheuvel" <ardb@kernel.org>,
"Nicolas Pitre" <nico@fluxnic.net>,
"Marek Szyprowski" <m.szyprowski@samsung.com>,
"Dmitry Osipenko" <digetx@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Simon Horman" <horms@verge.net.au>,
"Arnd Bergmann" <arnd@arndb.de>,
"Stephen Boyd" <sboyd@kernel.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Lukasz Stelmach" <l.stelmach@samsung.com>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
kexec@lists.infradead.org
Subject: Re: [PATCH v3] ARM: Parse kdump DT properties
Date: Thu, 6 May 2021 14:43:26 +0200 [thread overview]
Message-ID: <CACRpkdb47SZ1npdp+MNiAz4WZZvfVZOeHcV3Scv5pK1QurT06A@mail.gmail.com> (raw)
In-Reply-To: <20210317113130.2554368-1-geert+renesas@glider.be>
On Wed, Mar 17, 2021 at 12:31 PM Geert Uytterhoeven
<geert+renesas@glider.be> wrote:
> Parse the following DT properties in the crash dump kernel, to provide a
> modern interface between kexec and the crash dump kernel:
> - linux,elfcorehdr: ELF core header segment, similar to the
> "elfcorehdr=" kernel parameter.
> - linux,usable-memory-range: Usable memory reserved for the crash dump
> kernel.
> This makes the memory reservation explicit. If present, Linux no
> longer needs to mask the program counter, and rely on the "mem="
> kernel parameter to obtain the start and size of usable memory.
>
> For backwards compatibility, the traditional method to derive the start
> of memory is still used if "linux,usable-memory-range" is absent, and
> the "elfcorehdr=" and "mem=" kernel parameters are still parsed.
>
> Loosely based on the ARM64 version by Akashi Takahiro.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
I like the approach overall.
I see Rob has some comments that need adressing.
The chosen.txt file needs an example of how to use this so people
can intuitively get it right if they want to play with it, it was at least
the first question in my head: how does that look in practice?
Yours,
Linus Walleij
WARNING: multiple messages have this Message-ID (diff)
From: Linus Walleij <linus.walleij@linaro.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: "Russell King" <linux@armlinux.org.uk>,
"Ard Biesheuvel" <ardb@kernel.org>,
"Nicolas Pitre" <nico@fluxnic.net>,
"Marek Szyprowski" <m.szyprowski@samsung.com>,
"Dmitry Osipenko" <digetx@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Simon Horman" <horms@verge.net.au>,
"Arnd Bergmann" <arnd@arndb.de>,
"Stephen Boyd" <sboyd@kernel.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Lukasz Stelmach" <l.stelmach@samsung.com>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
kexec@lists.infradead.org
Subject: Re: [PATCH v3] ARM: Parse kdump DT properties
Date: Thu, 6 May 2021 14:43:26 +0200 [thread overview]
Message-ID: <CACRpkdb47SZ1npdp+MNiAz4WZZvfVZOeHcV3Scv5pK1QurT06A@mail.gmail.com> (raw)
In-Reply-To: <20210317113130.2554368-1-geert+renesas@glider.be>
On Wed, Mar 17, 2021 at 12:31 PM Geert Uytterhoeven
<geert+renesas@glider.be> wrote:
> Parse the following DT properties in the crash dump kernel, to provide a
> modern interface between kexec and the crash dump kernel:
> - linux,elfcorehdr: ELF core header segment, similar to the
> "elfcorehdr=" kernel parameter.
> - linux,usable-memory-range: Usable memory reserved for the crash dump
> kernel.
> This makes the memory reservation explicit. If present, Linux no
> longer needs to mask the program counter, and rely on the "mem="
> kernel parameter to obtain the start and size of usable memory.
>
> For backwards compatibility, the traditional method to derive the start
> of memory is still used if "linux,usable-memory-range" is absent, and
> the "elfcorehdr=" and "mem=" kernel parameters are still parsed.
>
> Loosely based on the ARM64 version by Akashi Takahiro.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
I like the approach overall.
I see Rob has some comments that need adressing.
The chosen.txt file needs an example of how to use this so people
can intuitively get it right if they want to play with it, it was at least
the first question in my head: how does that look in practice?
Yours,
Linus Walleij
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Linus Walleij <linus.walleij@linaro.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: "Russell King" <linux@armlinux.org.uk>,
"Ard Biesheuvel" <ardb@kernel.org>,
"Nicolas Pitre" <nico@fluxnic.net>,
"Marek Szyprowski" <m.szyprowski@samsung.com>,
"Dmitry Osipenko" <digetx@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Simon Horman" <horms@verge.net.au>,
"Arnd Bergmann" <arnd@arndb.de>,
"Stephen Boyd" <sboyd@kernel.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Lukasz Stelmach" <l.stelmach@samsung.com>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
kexec@lists.infradead.org
Subject: Re: [PATCH v3] ARM: Parse kdump DT properties
Date: Thu, 6 May 2021 14:43:26 +0200 [thread overview]
Message-ID: <CACRpkdb47SZ1npdp+MNiAz4WZZvfVZOeHcV3Scv5pK1QurT06A@mail.gmail.com> (raw)
In-Reply-To: <20210317113130.2554368-1-geert+renesas@glider.be>
On Wed, Mar 17, 2021 at 12:31 PM Geert Uytterhoeven
<geert+renesas@glider.be> wrote:
> Parse the following DT properties in the crash dump kernel, to provide a
> modern interface between kexec and the crash dump kernel:
> - linux,elfcorehdr: ELF core header segment, similar to the
> "elfcorehdr=" kernel parameter.
> - linux,usable-memory-range: Usable memory reserved for the crash dump
> kernel.
> This makes the memory reservation explicit. If present, Linux no
> longer needs to mask the program counter, and rely on the "mem="
> kernel parameter to obtain the start and size of usable memory.
>
> For backwards compatibility, the traditional method to derive the start
> of memory is still used if "linux,usable-memory-range" is absent, and
> the "elfcorehdr=" and "mem=" kernel parameters are still parsed.
>
> Loosely based on the ARM64 version by Akashi Takahiro.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
I like the approach overall.
I see Rob has some comments that need adressing.
The chosen.txt file needs an example of how to use this so people
can intuitively get it right if they want to play with it, it was at least
the first question in my head: how does that look in practice?
Yours,
Linus Walleij
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2021-05-06 12:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 11:31 [PATCH v3] ARM: Parse kdump DT properties Geert Uytterhoeven
2021-03-17 11:31 ` Geert Uytterhoeven
2021-03-17 11:31 ` Geert Uytterhoeven
2021-03-22 16:58 ` Rob Herring
2021-03-22 16:58 ` Rob Herring
2021-03-22 16:58 ` Rob Herring
2021-06-15 14:51 ` Geert Uytterhoeven
2021-06-15 14:51 ` Geert Uytterhoeven
2021-06-15 14:51 ` Geert Uytterhoeven
2021-05-06 12:43 ` Linus Walleij [this message]
2021-05-06 12:43 ` Linus Walleij
2021-05-06 12:43 ` Linus Walleij
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=CACRpkdb47SZ1npdp+MNiAz4WZZvfVZOeHcV3Scv5pK1QurT06A@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=l.stelmach@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=nico@fluxnic.net \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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.