From: Kairui Song <kasong@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
hpa@zytor.com, x86@kernel.org, dyoung@redhat.com, bhe@redhat.com,
kexec@lists.infradead.org, akpm@linux-foundation.org,
robert.moore@intel.com, erik.schmauss@intel.com,
rafael.j.wysocki@intel.com, lenb@kernel.org,
fanc.fnst@cn.fujitsu.com, linux-acpi@vger.kernel.org,
Kairui Song <kasong@redhat.com>
Subject: [PATCH v3 0/3] make kexec work with efi=noruntime or efi=old_map
Date: Fri, 18 Jan 2019 19:13:07 +0800 [thread overview]
Message-ID: <20190118111310.29589-1-kasong@redhat.com> (raw)
This patch series fix the kexec panic on efi=noruntime or efi=old_map
pass acpi_rsdp_addr to the second kernel and make it boot up properly.
Update from V2:
- Store acpi rsdp value, and add an acpi_os_get_root_pointer_late as
a helper, leveraging existing codes so we don't need to reparse RSDP.
Update from V1:
- Add a cover letter and fix some type in commit message
- Previous patches are not sent in a single thread
Kairui Song (3):
x86, kexec_file_load: Don't setup EFI info if EFI runtime is not
enabled
acpi: store acpi_rsdp address for later kexec usage
x86, kexec_file_load: make it work with efi=noruntime or efi=old_map
arch/x86/kernel/kexec-bzimage64.c | 13 +++++++++++++
drivers/acpi/osl.c | 10 ++++++++++
include/linux/acpi.h | 3 +++
3 files changed, 26 insertions(+)
--
2.20.1
next reply other threads:[~2019-01-18 11:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 11:13 Kairui Song [this message]
2019-01-18 11:13 ` [PATCH v3 1/3] x86, kexec_file_load: Don't setup EFI info if EFI runtime is not enabled Kairui Song
2019-01-25 2:53 ` Dave Young
2019-01-18 11:13 ` [PATCH v3 2/3] acpi: store acpi_rsdp address for later kexec usage Kairui Song
2019-01-18 11:26 ` Borislav Petkov
2019-01-18 11:43 ` Kairui Song
2019-01-18 11:13 ` [PATCH v3 3/3] x86, kexec_file_load: make it work with efi=noruntime or efi=old_map 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=20190118111310.29589-1-kasong@redhat.com \
--to=kasong@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=dyoung@redhat.com \
--cc=erik.schmauss@intel.com \
--cc=fanc.fnst@cn.fujitsu.com \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rafael.j.wysocki@intel.com \
--cc=robert.moore@intel.com \
--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).