[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cbe93b95-5bde-c77f-4984-fb982a3cb24f@ce.jp.nec.com>
Date: Tue, 2 Apr 2019 10:22:08 +0000
From: Junichi Nomura <j-nomura@...jp.nec.com>
To: Chao Fan <fanc.fnst@...fujitsu.com>
CC: Borislav Petkov <bp@...en8.de>, "bhe@...hat.com" <bhe@...hat.com>,
"Dave Young" <dyoung@...hat.com>,
"kasong@...hat.com" <kasong@...hat.com>,
"x86@...nel.org" <x86@...nel.org>,
"kexec@...ts.infradead.org" <kexec@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] x86/boot: Use efi_setup_data for searching RSDP on
kexec-ed kernel
On 4/2/19 8:06 PM, Chao Fan wrote:
> On Tue, Apr 02, 2019 at 09:53:51AM +0000, Junichi Nomura wrote:
>> On Tue, Apr 02, 2019 at 05:41:49PM +0800, Chao Fan wrote:
>>> [ 77.989030] kexec_core: Starting new kernel
>>> early console in extract_kernel
>>> input_data: 0x000000017f6033b1
>>> input_len: 0x00000000008412d4
>>> output: 0x000000017e000000
>>> output_len: 0x0000000001e15844
>>> kernel_total_size: 0x0000000001e2c000
>>> trampoline_32bit: 0x000000000009d000
>>> booted via startup_64()
>>>
>>>
>>> Physical KASLR disabled: no suitable memory region!
>>> ------
>>>
>>> I am not sure whether I have done the right test.
>>> This guest is booted from EFI. Here we can see the kexeced kernel
>>> has completed the compressed boot stage. So I think your PATCH works.
>>
>> Thanks for testing. If your test bed doesn't boot even with the patch,
>> you could check what was found as RSDP with a debug patch like below.
>
> Oh no, it booted. I just put the compressed stag log.
Ah, then I think the patch worked as expected. Thanks.
--
Jun'ichi Nomura, NEC Corporation / NEC Solution Innovators, Ltd.
Powered by blists - more mailing lists