From: Joel Stanley <joel@jms.id.au> To: Andrew Jeffery <andrew@aj.id.au> Cc: Rob Herring <robh+dt@kernel.org>, devicetree <devicetree@vger.kernel.org>, Linux ARM <linux-arm-kernel@lists.infradead.org>, linux-aspeed <linux-aspeed@lists.ozlabs.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org> Subject: Re: [PATCH v2 5/6] ARM: dts: rainier: Add reserved memory for ramoops Date: Thu, 19 Nov 2020 05:17:32 +0000 [thread overview] Message-ID: <CACPK8XfaF_ZzhL1mQxK5Rcpkq9UmBtas+MzxJvFTFC3Bm2UGuw@mail.gmail.com> (raw) In-Reply-To: <20201022014731.2035438-6-andrew@aj.id.au> On Thu, 22 Oct 2020 at 01:48, Andrew Jeffery <andrew@aj.id.au> wrote: > > Reserve a 1.5MiB region of memory to record kmsg dumps, console and > userspace message state into 16kiB ring-buffer slots. The sizing allows > for up to 16 dumps to be captured and read out. > > Set max-reason to KMSG_DUMP_EMERG to capture bad-path reboots. > > Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Reviewed-by: Joel Stanley <joel@jms.id.au> > --- > arch/arm/boot/dts/aspeed-bmc-ibm-rainier.dts | 9 +++++++++ > 1 file changed, 9 insertions(+) > > diff --git a/arch/arm/boot/dts/aspeed-bmc-ibm-rainier.dts b/arch/arm/boot/dts/aspeed-bmc-ibm-rainier.dts > index 802027a3c43c..8431cf1b32e6 100644 > --- a/arch/arm/boot/dts/aspeed-bmc-ibm-rainier.dts > +++ b/arch/arm/boot/dts/aspeed-bmc-ibm-rainier.dts > @@ -55,6 +55,15 @@ flash_memory: region@B8000000 { > > /* 48MB region from the end of flash to start of vga memory */ > > + ramoops@bc000000 { > + compatible = "ramoops"; > + reg = <0xbc000000 0x180000>; /* 16 * (3 * 0x8000) */ > + record-size = <0x8000>; > + console-size = <0x8000>; > + pmsg-size = <0x8000>; > + max-reason = <3>; /* KMSG_DUMP_EMERG */ > + }; > + > /* VGA region is dictated by hardware strapping */ > vga_memory: region@bf000000 { > no-map; > -- > 2.25.1 >
WARNING: multiple messages have this Message-ID (diff)
From: Joel Stanley <joel@jms.id.au> To: Andrew Jeffery <andrew@aj.id.au> Cc: devicetree <devicetree@vger.kernel.org>, Rob Herring <robh+dt@kernel.org>, linux-aspeed <linux-aspeed@lists.ozlabs.org>, Linux ARM <linux-arm-kernel@lists.infradead.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org> Subject: Re: [PATCH v2 5/6] ARM: dts: rainier: Add reserved memory for ramoops Date: Thu, 19 Nov 2020 05:17:32 +0000 [thread overview] Message-ID: <CACPK8XfaF_ZzhL1mQxK5Rcpkq9UmBtas+MzxJvFTFC3Bm2UGuw@mail.gmail.com> (raw) In-Reply-To: <20201022014731.2035438-6-andrew@aj.id.au> On Thu, 22 Oct 2020 at 01:48, Andrew Jeffery <andrew@aj.id.au> wrote: > > Reserve a 1.5MiB region of memory to record kmsg dumps, console and > userspace message state into 16kiB ring-buffer slots. The sizing allows > for up to 16 dumps to be captured and read out. > > Set max-reason to KMSG_DUMP_EMERG to capture bad-path reboots. > > Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Reviewed-by: Joel Stanley <joel@jms.id.au> > --- > arch/arm/boot/dts/aspeed-bmc-ibm-rainier.dts | 9 +++++++++ > 1 file changed, 9 insertions(+) > > diff --git a/arch/arm/boot/dts/aspeed-bmc-ibm-rainier.dts b/arch/arm/boot/dts/aspeed-bmc-ibm-rainier.dts > index 802027a3c43c..8431cf1b32e6 100644 > --- a/arch/arm/boot/dts/aspeed-bmc-ibm-rainier.dts > +++ b/arch/arm/boot/dts/aspeed-bmc-ibm-rainier.dts > @@ -55,6 +55,15 @@ flash_memory: region@B8000000 { > > /* 48MB region from the end of flash to start of vga memory */ > > + ramoops@bc000000 { > + compatible = "ramoops"; > + reg = <0xbc000000 0x180000>; /* 16 * (3 * 0x8000) */ > + record-size = <0x8000>; > + console-size = <0x8000>; > + pmsg-size = <0x8000>; > + max-reason = <3>; /* KMSG_DUMP_EMERG */ > + }; > + > /* VGA region is dictated by hardware strapping */ > vga_memory: region@bf000000 { > no-map; > -- > 2.25.1 > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-11-19 5:18 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-22 1:47 [PATCH v2 0/6] ARM: dts: Enable ramoops for Rainier and Tacoma Andrew Jeffery 2020-10-22 1:47 ` Andrew Jeffery 2020-10-22 1:47 ` [PATCH v2 1/6] ARM: dts: tacoma: Fix node vs reg mismatch for flash memory Andrew Jeffery 2020-10-22 1:47 ` Andrew Jeffery 2020-11-19 5:16 ` Joel Stanley 2020-11-19 5:16 ` Joel Stanley 2020-10-22 1:47 ` [PATCH v2 2/6] ARM: dts: tacoma: Zero-pad flash memory region length Andrew Jeffery 2020-10-22 1:47 ` Andrew Jeffery 2020-10-22 1:47 ` [PATCH v2 3/6] ARM: dts: rainier,tacoma: Fix size comment whitespace Andrew Jeffery 2020-10-22 1:47 ` Andrew Jeffery 2020-10-22 1:47 ` [PATCH v2 4/6] ARM: dts: rainier,tacoma: Comment reserved memory regions Andrew Jeffery 2020-10-22 1:47 ` [PATCH v2 4/6] ARM: dts: rainier, tacoma: " Andrew Jeffery 2020-10-22 1:47 ` [PATCH v2 5/6] ARM: dts: rainier: Add reserved memory for ramoops Andrew Jeffery 2020-10-22 1:47 ` Andrew Jeffery 2020-11-19 5:17 ` Joel Stanley [this message] 2020-11-19 5:17 ` Joel Stanley 2020-10-22 1:47 ` [PATCH v2 6/6] ARM: dts: tacoma: " Andrew Jeffery 2020-10-22 1:47 ` Andrew Jeffery 2020-11-19 5:18 ` Joel Stanley 2020-11-19 5:18 ` Joel Stanley
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=CACPK8XfaF_ZzhL1mQxK5Rcpkq9UmBtas+MzxJvFTFC3Bm2UGuw@mail.gmail.com \ --to=joel@jms.id.au \ --cc=andrew@aj.id.au \ --cc=devicetree@vger.kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-aspeed@lists.ozlabs.org \ --cc=linux-kernel@vger.kernel.org \ --cc=robh+dt@kernel.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.