kexec.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: Dave Young <dyoung@redhat.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Matt Fleming <matt@codeblueprint.co.uk>,
	Bhupesh Sharma <bhsharma@redhat.com>,
	kexec@lists.infradead.org, James Morse <james.morse@arm.com>,
	Bhupesh SHARMA <bhupesh.linux@gmail.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: arm64 crashkernel fails to boot on acpi-only machines due to ACPI regions being no longer mapped as NOMAP
Date: Tue, 9 Jan 2018 14:02:18 +0900	[thread overview]
Message-ID: <20180109050216.GB18820@linaro.org> (raw)
In-Reply-To: <20171226065636.GA5354@dhcp-128-65.nay.redhat.com>

On Tue, Dec 26, 2017 at 02:56:36PM +0800, Dave Young wrote:
> On 12/26/17 at 11:28am, AKASHI Takahiro wrote:
> > 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?).)
> 
> Hmm, I did a quick test with qemu/kvm, kdump kernel boot without numa=off
> I'm not sure why I do not see the warning messages on x86
> machines, maybe something arm64 specific?

I didn't see the messages(i.e. "potential offnode page_structs")
on arm64 qemu (with -smp 2 -numa node -numa node).

It seems that qemu doesn't generate acpi slit(inter-node distance table).

Thanks,
-Takahiro AKASHI

> > 
> > -Takahiro AKASHI

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

      reply	other threads:[~2018-01-09  4:57 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20171116070005.GI29552@linaro.org>
     [not found] ` <CAFTCetQHmpprAVu6uYO+rc5Xi4EUVhmovbmSaU6nM1n1mAH62w@mail.gmail.com>
     [not found]   ` <CAKv+Gu9oda1Ee8AoXsCEw+Bjn-XF3wZA_CsxvqhjtT6_bmJ7uA@mail.gmail.com>
     [not found]     ` <CACi5LpOZ=WOx14gTwH5jfLozepT2Jw8JSY5x+bfEZ_YaiQvFpw@mail.gmail.com>
     [not found]       ` <20171213102624.GC28046@linaro.org>
     [not found]         ` <CAKv+Gu_BmFN9Zg861SCS+R=V4khFykjuOzkmfEknsL=NvWW3Eg@mail.gmail.com>
     [not found]           ` <20171213121605.GE28046@linaro.org>
     [not found]             ` <CAKv+Gu_G8kBEAdAznVauZVAdJOFkr1vmu0Gf6tOwJfH2CgdufA@mail.gmail.com>
     [not found]               ` <20171215085924.sqlcwm4copzba5ag@fireball>
     [not found]                 ` <CAKv+Gu-W5VpVrgA=FVZCCevksaRGOVvPdE+B8WkpZc6AE1jOPw@mail.gmail.com>
     [not found]                   ` <CACi5LpPDL0j4o3MuOZ3jRv3UOqM48yTgKtdm-hY+OWL8h-ETzQ@mail.gmail.com>
2017-12-18  5:16                     ` arm64 crashkernel fails to boot on acpi-only machines due to ACPI regions being no longer mapped as NOMAP Dave Young
2017-12-18  5:54                       ` AKASHI Takahiro
2017-12-18  8:59                         ` Bhupesh SHARMA
2017-12-18 11:18                           ` AKASHI Takahiro
2017-12-18 22:28                             ` Bhupesh Sharma
2017-12-19  5:01                           ` AKASHI Takahiro
2017-12-20 19:52                             ` Bhupesh Sharma
2017-12-18 21:28                       ` Bhupesh Sharma
2017-12-19  5:25                         ` AKASHI Takahiro
     [not found]                 ` <20171218054009.GA6392@dhcp-128-65.nay.redhat.com>
2017-12-18  5:43                   ` Dave Young
     [not found]                   ` <20171219060927.GH28046@linaro.org>
     [not found]                     ` <CAKv+Gu-gmbWdZ7rxp5qGrtSBQ7dM=3FqF-Pw=J0LaL=oKTMg4w@mail.gmail.com>
     [not found]                       ` <CACi5LpOscbcBecWaC3Q9P22kheRYc+M2Ynfusszk14fPY-cJ5A@mail.gmail.com>
2017-12-21 10:34                         ` AKASHI Takahiro
2017-12-21 12:06                           ` Bhupesh Sharma
2017-12-22  8:33                             ` AKASHI Takahiro
2017-12-23 19:51                               ` Bhupesh Sharma
2017-12-25  3:25                                 ` AKASHI Takahiro
2017-12-25 20:14                                   ` Bhupesh Sharma
2017-12-26  1:32                                     ` Dave Young
2017-12-26  1:35                                       ` Dave Young
2017-12-26  2:28                                         ` AKASHI Takahiro
2017-12-26  2:56                                           ` Bhupesh Sharma
2017-12-26  6:58                                             ` Dave Young
2018-01-09  5:22                                               ` AKASHI Takahiro
2018-01-08 20:00                                             ` Bhupesh Sharma
2018-01-09  4:42                                               ` AKASHI Takahiro
2018-01-09 11:46                                                 ` Bhupesh Sharma
2017-12-26  6:56                                           ` Dave Young
2018-01-09  5:02                                             ` AKASHI Takahiro [this message]

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=20180109050216.GB18820@linaro.org \
    --to=takahiro.akashi@linaro.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=bhsharma@redhat.com \
    --cc=bhupesh.linux@gmail.com \
    --cc=dyoung@redhat.com \
    --cc=james.morse@arm.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=matt@codeblueprint.co.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).