From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124])
 by mx.groups.io with SMTP id smtpd.web10.8203.1618835552322007900
 for <devel@edk2.groups.io>;
 Mon, 19 Apr 2021 05:32:32 -0700
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=EAATwWW0;
 spf=pass (domain: redhat.com, ip: 170.10.133.124, mailfrom: lersek@redhat.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
	s=mimecast20190719; t=1618835551;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:
	 in-reply-to:in-reply-to:references:references;
	bh=1guMoJ1yKFDdYcJCiKOTh9i739/d+43M6Jfe6z3Tfm4=;
	b=EAATwWW0YEzMJtwxqRrZdTkT59QldFP+IK0PCZZFT7vqtVCyKbgJ5imOgf1YPBp2c+g5R4
	r69H+AP7s3Ww27+ED20p2/hfYEYeZBrFMu39ojce/Tye/X5hIDChgXMjhjM5rdYX/VX4jP
	QlZBVCKiN3dpTSEPWzczTKXYVnOvFKg=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com
 [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id
 us-mta-292-oO-YQ2wdPNq0wMfAWdFd0A-1; Mon, 19 Apr 2021 08:32:27 -0400
X-MC-Unique: oO-YQ2wdPNq0wMfAWdFd0A-1
Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 039D384BA42;
	Mon, 19 Apr 2021 12:32:27 +0000 (UTC)
Received: from lacos-laptop-7.usersys.redhat.com (ovpn-114-58.ams2.redhat.com [10.36.114.58])
	by smtp.corp.redhat.com (Postfix) with ESMTP id 4F41A60937;
	Mon, 19 Apr 2021 12:32:26 +0000 (UTC)
Subject: Re: [edk2-devel] The status of ACPI S4 support in OVMF
To: devel@edk2.groups.io, glin@suse.com
References: <YH1TYRjlXpj79fVw@GaryWorkstation>
From: "Laszlo Ersek" <lersek@redhat.com>
Message-ID: <340b613d-1f8e-ffb2-05a0-e41541301bd2@redhat.com>
Date: Mon, 19 Apr 2021 14:32:25 +0200
MIME-Version: 1.0
In-Reply-To: <YH1TYRjlXpj79fVw@GaryWorkstation>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13
Authentication-Results: relay.mimecast.com;
	auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=lersek@redhat.com
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit

On 04/19/21 11:54, Gary Lin via groups.io wrote:
> Hi,
>
> Years ago, the bug(*) for PEI variable driver was filed against OVMF
> and it used to be one reason to block S4 support in OVMF. The bug is
> fixed now, and there are several MemTypeInfo fixes merged into OVMF.
>
> I'm curious about the current status of S4 support in OVMF. Is it
> still considered as unsupported due to some other bugs?
>
> Thanks,
>
> Gary Lin
>
> (*) https://bugzilla.tianocore.org/show_bug.cgi?id=386

I recall the last related discussion from February:

* [edk2-devel] [PATCH 0/2] Improve hibernation safety

  https://edk2.groups.io/g/devel/message/71790
  https://listman.redhat.com/archives/edk2-devel-archive/2021-February/msg00842.html
  http://mid.mail-archive.com/20210218200953.20943-1-graf@amazon.com

No patches needed to be merged (Alex was missing some commits that had
been upstreamed by then).

My understanding is that S4 should work at this point, although I've
never really tested it myself.

Thanks
Laszlo