From: hanjun.guo@linaro.org (Hanjun Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM64 kexec/kdump timeline
Date: Thu, 28 May 2015 11:22:57 +0800 [thread overview]
Message-ID: <55668A11.1010304@linaro.org> (raw)
In-Reply-To: <CAKv+Gu8U1SWPb-GJ-3u9t_EX3g18AvOWisK3FycvRWsEdyjpzQ@mail.gmail.com>
On 2015?05?27? 17:38, Ard Biesheuvel wrote:
> On 27 May 2015 at 05:08, Timur Tabi <timur@codeaurora.org> wrote:
>> On 05/21/2015 03:15 PM, Geoff Levand wrote:
>>>
>>> I feel kexec was ready to merge nine months ago. Users have only sent
>>> private e-mails like yourself, so there has been no public inquiries,
>>> and so, the arm64 maintainers think kexec is not of interest to users.
>>
>>
>> Does kexec on ARM64 support ACPI? In some of our initial tests, it appears
>> that the kexec'd kernel won't boot because it's expecting a device tree, and
>> we don't have one.
>>
>> ARM64 servers are supposed to use ACPI instead of a device tree.
>>
>
> The latest arm64 kexec patches support booting via UEFI, and when
> booting via UEFI, the ACPI root pointer is retrieved from a UEFI
> configuration table if the FDT contains no system description. So ACPI
> support should not depend at all on how kexec is implemented (unless
> your FDT does contain a system description, in which case you should
> pass along the 'acpi=xxx' param that was given to the cold booted
> kernel)
Thanks for the clarify. Geoff also tested kexec on FVP with ACPI
enabled and it works as far as I know.
Timur, can you provide more detailed information then we can debug
into it?
Thanks
Hanjun
next prev parent reply other threads:[~2015-05-28 3:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <555E37FC.9020800@codeaurora.org>
[not found] ` <1432239334.1922.7.camel@infradead.org>
2015-05-27 3:08 ` ARM64 kexec/kdump timeline Timur Tabi
2015-05-27 9:38 ` Ard Biesheuvel
2015-05-28 3:22 ` Hanjun Guo [this message]
2015-05-28 16:49 ` Geoff Levand
2015-05-27 16:32 ` Geoff Levand
2015-05-27 16:39 ` Arnd Bergmann
2015-05-27 23:14 ` Timur Tabi
2015-05-28 3:52 ` Hanjun Guo
2015-05-28 7:16 ` Ard Biesheuvel
2015-06-01 6:25 ` Pratyush Anand
2015-06-29 23:20 ` Timur Tabi
2015-07-08 23:03 ` Azriel Samson
[not found] ` <CAB5YjtCCO3vB6hrktL9wmpSP6mmtHGd-TQhYK3GnS1eQ7-XU-w@mail.gmail.com>
2015-12-04 21:53 ` Azriel Samson
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=55668A11.1010304@linaro.org \
--to=hanjun.guo@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).