From: Junichi Nomura <j-nomura@ce.jp.nec.com>
To: Kairui Song <kasong@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Borislav Petkov" <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
Chao Fan <fanc.fnst@cn.fujitsu.com>, Baoquan He <bhe@redhat.com>,
Dave Young <dyoung@redhat.com>, "x86@kernel.org" <x86@kernel.org>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: Re: [PATCH] x86/kexec: always ensure EFI systab region is mapped
Date: Wed, 24 Apr 2019 02:47:32 +0000 [thread overview]
Message-ID: <24f1dc7c-1dea-79b0-d364-0dc7d605ce01@ce.jp.nec.com> (raw)
In-Reply-To: <CACPcB9d-oNvp1Kag1J8X+QBdgqfU0ps1OztjOk8n=Pw2G6ONWA@mail.gmail.com>
On 4/24/19 2:15 AM, Kairui Song wrote:
> On Mon, Apr 22, 2019 at 11:21 PM Junichi Nomura <j-nomura@ce.jp.nec.com> wrote:
>> Is the mapping of ACPI tables just by luck, too?
>
> Good question, they should have same issue with systab, I ignored this one.
> Then in first kernel when doing kexec it should ensure both ACPI
> tables and the EFI systab are mapped, that should cover everything and
> make it work.
Right.
> Is there anything else missing?
No, as far as I looked around get_rsdp_addr().
--
Jun'ichi Nomura, NEC Corporation / NEC Solution Innovators, Ltd.
next prev parent reply other threads:[~2019-04-24 2:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-22 9:28 [PATCH] x86/kexec: always ensure EFI systab region is mapped Kairui Song
2019-04-23 6:20 ` Junichi Nomura
2019-04-23 10:49 ` Dave Young
2019-04-23 17:15 ` Kairui Song
2019-04-24 2:47 ` Junichi Nomura [this message]
2019-04-24 5:41 ` Baoquan He
2019-04-24 6:18 ` Dave Young
2019-04-24 7:45 ` Baoquan He
2019-04-24 11:36 ` Kairui Song
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=24f1dc7c-1dea-79b0-d364-0dc7d605ce01@ce.jp.nec.com \
--to=j-nomura@ce.jp.nec.com \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=dyoung@redhat.com \
--cc=fanc.fnst@cn.fujitsu.com \
--cc=kasong@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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: 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).