[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200101062047.GA16393@dhcp-128-65.nay.redhat.com>
Date: Wed, 1 Jan 2020 14:20:47 +0800
From: Dave Young <dyoung@...hat.com>
To: Dan Williams <dan.j.williams@...el.com>
Cc: Ingo Molnar <mingo@...hat.com>,
Taku Izumi <izumi.taku@...fujitsu.com>,
Michael Weiser <michael@...ser.dinsnail.net>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-efi <linux-efi@...r.kernel.org>, kexec@...ts.infradead.org,
X86 ML <x86@...nel.org>
Subject: Re: [PATCH v2 4/4] efi: Fix handling of multiple efi_fake_mem=
entries
> > Does kexec preserve iomem? I.e. as long as the initial translation of
> > efi entries to e820, and resulting resource tree, is preserved by
> > successive kexec cycles then I think we're ok.
>
> It will not preserve them automatically, but that can be fixed if
> needed.
>
> There are two places:
> 1. the in kernel loader, we can do similar with below commit (for Soft
> Reseved instead):
> commit 980621daf368f2b9aa69c7ea01baa654edb7577b
> Author: Lianbo Jiang <lijiang@...hat.com>
> Date: Tue Apr 23 09:30:07 2019 +0800
>
> x86/crash: Add e820 reserved ranges to kdump kernel's e820 table
Oops, that is for kdump only, for kexec, should update the kexec e820
table. But before doing that we need first to see if this is necessary.
Thanks
Dave
Powered by blists - more mailing lists