From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <lersek@redhat.com>
Received-SPF: Pass (sender SPF authorized) identity=mailfrom;
 client-ip=209.132.183.28; helo=mx1.redhat.com; envelope-from=lersek@redhat.com;
 receiver=edk2-devel@lists.01.org 
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by ml01.01.org (Postfix) with ESMTPS id 52ADC211B698D
 for <edk2-devel@lists.01.org>; Fri, 11 Jan 2019 02:14:08 -0800 (PST)
Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com
 [10.5.11.16])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.redhat.com (Postfix) with ESMTPS id B403C2D7E0;
 Fri, 11 Jan 2019 10:14:07 +0000 (UTC)
Received: from lacos-laptop-7.usersys.redhat.com (ovpn-120-3.rdu2.redhat.com
 [10.10.120.3])
 by smtp.corp.redhat.com (Postfix) with ESMTP id 749985C221;
 Fri, 11 Jan 2019 10:14:06 +0000 (UTC)
To: =?UTF-8?B?6rmA7ZiB7KSR?= <wangmir@gmail.com>
References: <CAAkw5-PTfTBTOx_Hu_JduVGyMtyzZTnxL6crn+JHwbVR45Lizg@mail.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>
From: Laszlo Ersek <lersek@redhat.com>
Message-ID: <7e68f21f-d749-b5a7-96c8-3c45257f4337@redhat.com>
Date: Fri, 11 Jan 2019 11:14:05 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <CAAkw5-PTfTBTOx_Hu_JduVGyMtyzZTnxL6crn+JHwbVR45Lizg@mail.gmail.com>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16
 (mx1.redhat.com [10.5.110.30]); Fri, 11 Jan 2019 10:14:07 +0000 (UTC)
Subject: Re: Support S3 on ARMVirtPkg
X-BeenThere: edk2-devel@lists.01.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: EDK II Development  <edk2-devel.lists.01.org>
List-Unsubscribe: <https://lists.01.org/mailman/options/edk2-devel>,
 <mailto:edk2-devel-request@lists.01.org?subject=unsubscribe>
List-Archive: <http://lists.01.org/pipermail/edk2-devel/>
List-Post: <mailto:edk2-devel@lists.01.org>
List-Help: <mailto:edk2-devel-request@lists.01.org?subject=help>
List-Subscribe: <https://lists.01.org/mailman/listinfo/edk2-devel>,
 <mailto:edk2-devel-request@lists.01.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jan 2019 10:14:08 -0000
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit

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