From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=2607:f8b0:4864:20::e30; helo=mail-vs1-xe30.google.com; envelope-from=wangmir@gmail.com; receiver=edk2-devel@lists.01.org Received: from mail-vs1-xe30.google.com (mail-vs1-xe30.google.com [IPv6:2607:f8b0:4864:20::e30]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 18EF3211B698D for ; Fri, 11 Jan 2019 02:29:20 -0800 (PST) Received: by mail-vs1-xe30.google.com with SMTP id n10so8876074vso.13 for ; Fri, 11 Jan 2019 02:29:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Lk59hLzF4AMVGGhOKVBIJF+a3zkUayxQwkvKCzyOQ7M=; b=k06vAaTcCb232voZ5FZTX77NiLhdkN2CdokyYf7cVZTdGVWuLhk/WwN3r/jsF+eG42 yZ9731LZAA7eKLKdBJEcTezfI3988OxXpt9REotkPQqWgi0/FdJdlRJlpQEHkZc17wPG uwkeX8w8AwcApqGbHDyNEjbMz6zvyKr018EJmEcrIXeQ4QzRSYdczaIGMlD9zsB28WD+ vmT90yUetNB0zGkIimKdaTcOAoSOofIYGAuTI7V44HeA5BSft1caW/pb1g37Ydk+lQy8 lkSuZx/BhRXn2Dtd3C12abo7CB+MN9m74bh1CNOrDa2wJwYvAjNIwoPl4RRW3+QwFjA6 xRNA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Lk59hLzF4AMVGGhOKVBIJF+a3zkUayxQwkvKCzyOQ7M=; b=nFm8qzIOodRBp0Yp5/g76q4nBnbgUsnFINd6enCZZK1wtKPvn+X0kSp04LKPRMk123 TqGXmPx/a4hFuw+bX/qW9SPP6F4Of7d7R9rrK2TRQAsEKIzvGA7LEVg81K8SHjB8Nvq4 tbvRcfbSPZRKgFp8SWWjGL2vwYTnPKmgPEBf6Olp6CVI+mFUvtKVzOugbYC60ZcxXQtb XBeHR8oKrsx4+LMyZA5Q8wCRfoS87Ml9p7ZdNYSV/gDU09ycPWYTM8TqFlp8BPbkGXJ0 tEl8J+BNInJ2uWxBzuRqTQbvnnUtqiDFhtEe4zU0CTDU96EluWjUxU6IZ3bsk6n6B3Jo edNQ== X-Gm-Message-State: AJcUukfxj3cpjnw6d4ulLsldE/5pKJm6sNE+YdZdvcDG+kWrA0uR8Ua5 68uwvVAgct6ZpsNVen+WMQ+q27Ex3OMLNbiKs9/uhw== X-Google-Smtp-Source: ALg8bN5Q4s3z/upfLxAgX+YKHXBrUu2fXbBzG97cbdeMBJzq6SIRB8bl7VONwjkRS1UgY63sCAjcIgghvtiHL2anyrU= X-Received: by 2002:a67:4dd4:: with SMTP id i81mr5714706vsg.46.1547202559791; Fri, 11 Jan 2019 02:29:19 -0800 (PST) MIME-Version: 1.0 References: <7e68f21f-d749-b5a7-96c8-3c45257f4337@redhat.com> In-Reply-To: <7e68f21f-d749-b5a7-96c8-3c45257f4337@redhat.com> From: =?UTF-8?B?6rmA7ZiB7KSR?= Date: Fri, 11 Jan 2019 19:29:10 +0900 Message-ID: To: Laszlo Ersek Cc: edk2-devel@lists.01.org, Leif Lindholm , Ard Biesheuvel , Grant Likely X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jan 2019 10:29:21 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Oh no, I only have qemu arm VM, not physical machine, with WoA (Windows on Arm), and I'm trying to enable suspend mode on windows but it failed, and i figured recently that it is because of acpi setting of qemu and its related edk2 functionality by comparing it with x64 VM. So, first of all, I thought that i need to implement some part of qemu acpi setting and its corrrsponding functionality, but after some of digging i realized that current edk2 for armvirtpkg also not support s3 features. So i reached to this mailing list. 2019=EB=85=84 1=EC=9B=94 11=EC=9D=BC (=EA=B8=88) =EC=98=A4=ED=9B=84 7:14=EC= =97=90 Laszlo Ersek =EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84= =B1: > On 01/11/19 09:17, =EA=B9=80=ED=98=81=EC=A4=91 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 >