From: Chao Fan <fanc.fnst@cn.fujitsu.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Kairui Song <kasong@redhat.com>, <linux-kernel@vger.kernel.org>,
<tglx@linutronix.de>, <mingo@redhat.com>, <hpa@zytor.com>,
<x86@kernel.org>, Dave Young <dyoung@redhat.com>,
Baoquan He <bhe@redhat.com>, <kexec@lists.infradead.org>,
<akpm@linux-foundation.org>, <robert.moore@intel.com>,
<erik.schmauss@intel.com>, <rafael.j.wysocki@intel.com>,
Len Brown <lenb@kernel.org>
Subject: Re: [PATCH v2 2/2] x86, kexec_file_load: make it work with efi=noruntime or efi=old_map
Date: Mon, 21 Jan 2019 09:18:30 +0800 [thread overview]
Message-ID: <20190121011830.GA1554@localhost.localdomain> (raw)
In-Reply-To: <20190118102636.GB622@zn.tnic>
On Fri, Jan 18, 2019 at 11:26:36AM +0100, Borislav Petkov wrote:
>On Thu, Jan 17, 2019 at 03:41:13PM +0800, Kairui Song wrote:
>> How about we refill the boot_params.acpi_rsdp_addr if it is not valid
>> in early code, so it could be used as a reliable RSDP address source?
>> That should make things easier.
>>
>> But if early code should parse it and store it should be done in
>> Chao's patch, or I can post another patch to do it if Chao's patch is
>> merged.
>
>Chao's stuff does the as early as possible parsing of RDSP. Then, it
>should be saved into boot_params and everything else should read it from
>there. Simple.
Hi Boris,
So I have changed as this method and put in my mail thread, you may not
notice, so I put here for my function if I need to fill the
boot_parameters:
static inline acpi_physical_address get_boot_params_rsdp(void)
{
return boot_params->acpi_rsdp_addr;
}
static acpi_physical_address get_rsdp_addr(void)
{
bool boot_params_rsdp_exist;
acpi_physical_address pa;
pa = get_acpi_rsdp();
if (!pa)
pa = get_boot_params_rsdp();
if (!pa) {
pa = efi_get_rsdp_addr();
boot_params_rsdp_exist = false;
}
else
boot_params_rsdp_exist = true;
if (!pa)
pa = bios_get_rsdp_addr();
if (pa && !boot_params_rsdp_exist)
boot_params.acpi_rsdp_addr = pa;
return pa;
}
At the same time, I notice kernel only parses it when
"#ifdef CONFIG_ACPI", we should keep sync with kernel, but I think
we are parsing SRAT, CONFIG_ACPI is needed sure, so I am going to
update the define of EARLY_SRAT_PARSE:
config EARLY_SRAT_PARSE
bool "EARLY SRAT parsing"
def_bool y
depends on RANDOMIZE_BASE && MEMORY_HOTREMOVE && ACPI
If I miss something, please let me know.
Or in my PATCHSET, I don't need to fill boot_parameters, just
leave the job another PATCH?
Thanks,
Chao Fan
>
>--
>Regards/Gruss,
> Boris.
>
>Good mailing practices for 400: avoid top-posting and trim the reply.
>
>
next prev parent reply other threads:[~2019-01-21 7:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 9:58 [PATCH 0/2] make kexec work with efi=noruntime or efi=old_map Kairui Song
2019-01-15 9:58 ` [PATCH v2 1/2] x86, kexec_file_load: Don't setup EFI info if EFI runtime is not enabled Kairui Song
2019-01-15 9:58 ` [PATCH v2 2/2] x86, kexec_file_load: make it work with efi=noruntime or efi=old_map Kairui Song
2019-01-15 23:10 ` Borislav Petkov
2019-01-16 3:32 ` Dave Young
2019-01-16 5:09 ` Kairui Song
2019-01-16 6:51 ` Dave Young
2019-01-16 22:24 ` Rafael J. Wysocki
2019-01-16 7:08 ` Kairui Song
2019-01-16 9:46 ` Borislav Petkov
2019-01-17 7:41 ` Kairui Song
2019-01-17 7:49 ` Chao Fan
2019-01-17 8:20 ` Kairui Song
2019-01-17 8:54 ` Dave Young
2019-01-17 8:53 ` Dave Young
2019-01-17 9:39 ` Rafael J. Wysocki
2019-01-18 4:47 ` Kairui Song
2019-01-18 9:45 ` Rafael J. Wysocki
2019-01-18 10:26 ` Borislav Petkov
2019-01-21 1:18 ` Chao Fan [this message]
2019-01-21 8:29 ` Borislav Petkov
2019-01-21 8:43 ` Chao Fan
2019-01-21 9:19 ` Borislav Petkov
2019-01-22 3:32 ` Chao Fan
2019-01-22 12:17 ` Borislav Petkov
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=20190121011830.GA1554@localhost.localdomain \
--to=fanc.fnst@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=dyoung@redhat.com \
--cc=erik.schmauss@intel.com \
--cc=hpa@zytor.com \
--cc=kasong@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=lenb@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