From: Laszlo Ersek <lersek@redhat.com>
To: 김혁중 <wangmir@gmail.com>
Cc: edk2-devel@lists.01.org, Leif Lindholm <leif.lindholm@linaro.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Grant Likely <grant.likely@arm.com>
Subject: Re: Support S3 on ARMVirtPkg
Date: Fri, 11 Jan 2019 11:14:05 +0100 [thread overview]
Message-ID: <7e68f21f-d749-b5a7-96c8-3c45257f4337@redhat.com> (raw)
In-Reply-To: <CAAkw5-PTfTBTOx_Hu_JduVGyMtyzZTnxL6crn+JHwbVR45Lizg@mail.gmail.com>
On 01/11/19 09:17, 김혁중 wrote:
> Hi all,
>
> I'm currently using edk2 for qemu arm emulation environment, and i have a
> question about s3 support for ArmVirtPkg.
>
> I read white paper about ovmf, and I'm trying to follow up the things about
> uefi and boot up procedure, but I don't know how to start to support
> suspend (S3) functionality from edk2 firmware cuz ArmVirtQemu.pkg is pretty
> different from x64 of it.
>
> And I could not find any current situation of supporting s3 on armvirt.
>
> So, can anyone tell me about current situation, or starting point to
> support s3 on armvirt?
I think edk2 lacks most of the S3 infrastructure for ARM/AARCH64. For
example, "MdeModulePkg/Universal/Acpi/BootScriptExecutorDxe" is strictly
IA32/X64. The same applies to "UefiCpuPkg/Universal/Acpi/S3Resume2Pei".
In fact, I don't even know if the "traditional S3" power state from the
ACPI spec applies to "Hardware-reduced ACPI"... Well, yes, that seems to
be the case: chapter "16 Waking and Sleeping" has several clauses
specific to HW-reduced ACPI.
Have you encountered a physical AARCH64 machine + OS combination that
supports ACPI S3?
Thanks
Laszlo
next prev parent reply other threads:[~2019-01-11 10:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 8:17 Support S3 on ARMVirtPkg 김혁중
2019-01-11 10:14 ` Laszlo Ersek [this message]
2019-01-11 10:29 ` 김혁중
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-list 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=7e68f21f-d749-b5a7-96c8-3c45257f4337@redhat.com \
--to=devel@edk2.groups.io \
/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