From: "Gerd Hoffmann" <kraxel@redhat.com>
To: devel@edk2.groups.io, sebastien.boeuf@intel.com
Cc: jiewen.yao@intel.com, jordan.l.justen@intel.com
Subject: Re: [edk2-devel] [PATCH] OvmfPkg: Update I/O port related to ACPI devices for CloudHv
Date: Mon, 15 Aug 2022 15:49:07 +0200 [thread overview]
Message-ID: <20220815134907.uhfr2h6yeoj6vpaa@sirius.home.kraxel.org> (raw)
In-Reply-To: <f31deea47384d97fc16dd6035e08a1798981b395.1660221505.git.sebastien.boeuf@intel.com>
On Thu, Aug 11, 2022 at 02:40:57PM +0200, Boeuf, Sebastien wrote:
> From: Sebastien Boeuf <sebastien.boeuf@intel.com>
>
> Both ACPI shutdown and ACPI PM timer devices has been moved to different
> port addresses in the latest version of Cloud Hypervisor. These changes
> need to be reflected on the OVMF firmware.
Can this be detected by the guest somehow, so the firmware can work with
both old+new cloudhv?
Requiring lockstep updates tends to be painful, so we try avoid that
with qemu ...
(just a suggestion, not an objection)
Acked-by: Gerd Hoffmann <kraxel@redhat.com>
take care,
Gerd
next prev parent reply other threads:[~2022-08-15 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 12:40 [PATCH] OvmfPkg: Update I/O port related to ACPI devices for CloudHv Boeuf, Sebastien
2022-08-15 13:49 ` Gerd Hoffmann [this message]
2022-08-19 9:55 ` [edk2-devel] " Boeuf, Sebastien
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=20220815134907.uhfr2h6yeoj6vpaa@sirius.home.kraxel.org \
--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