From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: devel@edk2.groups.io, Ard Biesheuvel <ardb+tianocore@kernel.org>,
Jiewen Yao <jiewen.yao@intel.com>,
Jordan Justen <jordan.l.justen@intel.com>,
Erdem Aktas <erdemaktas@google.com>,
James Bottomley <jejb@linux.ibm.com>,
Min Xu <min.m.xu@intel.com>, Michael Roth <michael.roth@amd.com>
Subject: Re: [edk2-devel] [PATCH] OvmfPkg/ResetVector: Fix assembler bit test flag check
Date: Tue, 19 Sep 2023 09:59:28 +0200 [thread overview]
Message-ID: <hu4g52ctgcbyvuol6y27tvcxr5xzs34pmysd5xapzcdaudurkz@srd6ornzqg2a> (raw)
In-Reply-To: <f1e2264e03edf91c1020b989e123c332d3754376.1689366506.git.thomas.lendacky@amd.com>
On Fri, Jul 14, 2023 at 03:28:26PM -0500, Tom Lendacky wrote:
> Commit 63c50d3ff2854a76432b752af4f2a76f33ff1974 changed the check that is
> used to determine if SEV-ES is active. Originally, a CMP instruction with
> a supporting JZ instruction was used for the check. It was changed to use
> the BT instruction but not JZ instruction. The result of a BT instruction
> changes the the carry flag (CF) and not the zero flag (ZF). As a result,
> the wrong condition is being checked. Update the JZ to a JNC to properly
> detect if SEV-ES is active.
What is the effect of this bug? Is it just the encryption sanity check
being skipped?
take care,
Gerd
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#108817): https://edk2.groups.io/g/devel/message/108817
Mute This Topic: https://groups.io/mt/100149226/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2023-09-19 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 20:28 [PATCH] OvmfPkg/ResetVector: Fix assembler bit test flag check Lendacky, Thomas
2023-07-15 0:26 ` Ard Biesheuvel
2023-09-19 7:59 ` Gerd Hoffmann [this message]
2023-09-19 13:19 ` [edk2-devel] " Lendacky, Thomas via groups.io
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=hu4g52ctgcbyvuol6y27tvcxr5xzs34pmysd5xapzcdaudurkz@srd6ornzqg2a \
--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