From: Lakshmi Ramasubramanian <nramas@linux.microsoft.com>
To: qemu-arm <qemu-arm@nongnu.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
qemu-devel@nongnu.org
Subject: Re: Is kexec supported in QEMU for ARM64 (qemu-system-aarch64) with arm-trusted-firmware, optee, and u-boot.
Date: Thu, 26 Sep 2019 15:35:56 -0700 [thread overview]
Message-ID: <ca5c74db-cf5d-0c3f-eb6f-27d1092420ae@linux.microsoft.com> (raw)
In-Reply-To: <21633062-b021-a8e7-0cc8-062f4c29dde5@linux.microsoft.com>
On 9/26/19 8:17 AM, Lakshmi Ramasubramanian wrote:
The following commit for ARM Trusted Firmware for QEMU virt ARMv8-A
is almost 3 years old
https://salsa.debian.org/debian/atf-allwinner/commit/b6b671c4ac4bd5595306863225bb3bece1e6135c
Current limitations:
* Only cold boot is supported
* No build instructions for QEMU_EFI.fd and rootfs-arm64.cpio.gz
* No instructions for how to load a BL32 (Secure Payload)
So looks like only cold boot is supported (no kexec support)
Is this correct?
> When I execute kexec ("kexec -l <kernel>", followed by "kexec -e") I hit
> the following assert (in arm-trusted-firmware/plat/qemu/qemu_pm.c)
>
> /*******************************************************************************
>
> * Platform handler called when a power domain is about to be turned
> * off. The target_state encodes the power state that each level should
> * transition to.
> ******************************************************************************/
>
> void qemu_pwr_domain_off(const psci_power_state_t *target_state)
> {
> assert(0);
> }
>
> Is kexec supported in ARM64 QEMU (qemu-system-aarch64) -
> using arm-trusted-firmware, optee, and u-boot?
>
> Thanks,
> -lakshmi
next parent reply other threads:[~2019-09-27 1:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <21633062-b021-a8e7-0cc8-062f4c29dde5@linux.microsoft.com>
2019-09-26 22:35 ` Lakshmi Ramasubramanian [this message]
2019-09-27 9:15 ` Is kexec supported in QEMU for ARM64 (qemu-system-aarch64) with arm-trusted-firmware, optee, and u-boot Philippe Mathieu-Daudé
2019-09-30 22:27 ` Lakshmi Ramasubramanian
2019-10-01 16:30 ` Ard Biesheuvel
2019-10-02 1:32 ` Lakshmi Ramasubramanian
2019-10-09 13:38 ` Ard Biesheuvel
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=ca5c74db-cf5d-0c3f-eb6f-27d1092420ae@linux.microsoft.com \
--to=nramas@linux.microsoft.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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).