From mboxrd@z Thu Jan 1 00:00:00 1970 From: AKASHI Takahiro Subject: Re: arm64 crashkernel fails to boot on acpi-only machines due to ACPI regions being no longer mapped as NOMAP Date: Tue, 26 Dec 2017 11:28:09 +0900 Message-ID: <20171226022807.GB8877@linaro.org> References: <20171221103440.GJ28046@linaro.org> <20171222083308.cy3vwlyhig22q5ee@fireball> <20171225032500.GA8877@linaro.org> <20171226013217.GA2119@dhcp-128-65.nay.redhat.com> <20171226013517.GA2186@dhcp-128-65.nay.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20171226013517.GA2186-0VdLhd/A9Pl+NNSt+8eSiB/sF2h8X+2i0E9HWUfgJXw@public.gmane.org> Sender: linux-efi-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Dave Young Cc: Bhupesh Sharma , Ard Biesheuvel , Bhupesh SHARMA , Matt Fleming , "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" , "linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Mark Rutland , James Morse , kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org List-Id: linux-efi@vger.kernel.org On Tue, Dec 26, 2017 at 09:35:17AM +0800, Dave Young wrote: > [snip] > > > > Well, we may be able to change pr_warn() to pr_warn_once() here, but > > > > I hope that adding "numa=off" to kernel command line should also work. > > > > > > Hmm, adding "numa=off" to crashkernel bootargs works, and TBH it was > > > my initial thought process as well, but I am not sure if this will > > > cause any regressions on aarch64 systems which use crashdump feature. > > > > It should be fine since we use numa=off by default for all other arches > > ie. x86, ppc64 and s390. Actually disabling numa in kdump kernel can save > > mm component memory usage. > > > > Forgot to say I means in RHEL and Fedora we use numa=off for kdump.. Thank you for the clarification. (It might be better to make numa off automatically if maxcpus == 0 (and 1?).) -Takahiro AKASHI From mboxrd@z Thu Jan 1 00:00:00 1970 From: takahiro.akashi@linaro.org (AKASHI Takahiro) Date: Tue, 26 Dec 2017 11:28:09 +0900 Subject: arm64 crashkernel fails to boot on acpi-only machines due to ACPI regions being no longer mapped as NOMAP In-Reply-To: <20171226013517.GA2186@dhcp-128-65.nay.redhat.com> References: <20171221103440.GJ28046@linaro.org> <20171222083308.cy3vwlyhig22q5ee@fireball> <20171225032500.GA8877@linaro.org> <20171226013217.GA2119@dhcp-128-65.nay.redhat.com> <20171226013517.GA2186@dhcp-128-65.nay.redhat.com> Message-ID: <20171226022807.GB8877@linaro.org> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Tue, Dec 26, 2017 at 09:35:17AM +0800, Dave Young wrote: > [snip] > > > > Well, we may be able to change pr_warn() to pr_warn_once() here, but > > > > I hope that adding "numa=off" to kernel command line should also work. > > > > > > Hmm, adding "numa=off" to crashkernel bootargs works, and TBH it was > > > my initial thought process as well, but I am not sure if this will > > > cause any regressions on aarch64 systems which use crashdump feature. > > > > It should be fine since we use numa=off by default for all other arches > > ie. x86, ppc64 and s390. Actually disabling numa in kdump kernel can save > > mm component memory usage. > > > > Forgot to say I means in RHEL and Fedora we use numa=off for kdump.. Thank you for the clarification. (It might be better to make numa off automatically if maxcpus == 0 (and 1?).) -Takahiro AKASHI From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-pg0-x235.google.com ([2607:f8b0:400e:c05::235]) by bombadil.infradead.org with esmtps (Exim 4.89 #1 (Red Hat Linux)) id 1eTeuD-0004Fd-A5 for kexec@lists.infradead.org; Tue, 26 Dec 2017 02:23:51 +0000 Received: by mail-pg0-x235.google.com with SMTP id g7so17345470pgs.0 for ; Mon, 25 Dec 2017 18:23:36 -0800 (PST) Date: Tue, 26 Dec 2017 11:28:09 +0900 From: AKASHI Takahiro Subject: Re: arm64 crashkernel fails to boot on acpi-only machines due to ACPI regions being no longer mapped as NOMAP Message-ID: <20171226022807.GB8877@linaro.org> References: <20171221103440.GJ28046@linaro.org> <20171222083308.cy3vwlyhig22q5ee@fireball> <20171225032500.GA8877@linaro.org> <20171226013217.GA2119@dhcp-128-65.nay.redhat.com> <20171226013517.GA2186@dhcp-128-65.nay.redhat.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20171226013517.GA2186@dhcp-128-65.nay.redhat.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "kexec" Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: Dave Young Cc: Mark Rutland , "linux-efi@vger.kernel.org" , Ard Biesheuvel , Matt Fleming , Bhupesh Sharma , kexec@lists.infradead.org, James Morse , Bhupesh SHARMA , "linux-arm-kernel@lists.infradead.org" On Tue, Dec 26, 2017 at 09:35:17AM +0800, Dave Young wrote: > [snip] > > > > Well, we may be able to change pr_warn() to pr_warn_once() here, but > > > > I hope that adding "numa=off" to kernel command line should also work. > > > > > > Hmm, adding "numa=off" to crashkernel bootargs works, and TBH it was > > > my initial thought process as well, but I am not sure if this will > > > cause any regressions on aarch64 systems which use crashdump feature. > > > > It should be fine since we use numa=off by default for all other arches > > ie. x86, ppc64 and s390. Actually disabling numa in kdump kernel can save > > mm component memory usage. > > > > Forgot to say I means in RHEL and Fedora we use numa=off for kdump.. Thank you for the clarification. (It might be better to make numa off automatically if maxcpus == 0 (and 1?).) -Takahiro AKASHI _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec