From: "Gary Lin" <glin@suse.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: devel@edk2.groups.io
Subject: Re: [edk2-devel] The status of ACPI S4 support in OVMF
Date: Tue, 20 Apr 2021 09:30:20 +0800 [thread overview]
Message-ID: <YH4urJjLOh1YILOg@GaryWorkstation> (raw)
In-Reply-To: <340b613d-1f8e-ffb2-05a0-e41541301bd2@redhat.com>
On Mon, Apr 19, 2021 at 02:32:25PM +0200, Laszlo Ersek wrote:
> 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 for the information. I was reviewing the libvirt descriptor for
ovmf and wondering if it's ready for the "acpi-s4" tag. Maybe it's a
good to give it a try.
Thanks,
Gary Lin
prev parent reply other threads:[~2021-04-20 1:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 9:54 The status of ACPI S4 support in OVMF Gary Lin
2021-04-19 12:32 ` [edk2-devel] " Laszlo Ersek
2021-04-20 1:30 ` Gary Lin [this message]
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=YH4urJjLOh1YILOg@GaryWorkstation \
--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