diff options
author | Lendacky, Thomas <thomas.lendacky@amd.com> | 2021-04-29 12:12:10 -0500 |
---|---|---|
committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | 2021-04-30 18:35:50 +0000 |
commit | 75d1a7903db171d80f9728b24274852ab613ed2b (patch) | |
tree | d818ca5cc58ffafafcedb448bdbc22e5f153d7ae /MdePkg/Test | |
parent | ab957f036f6711869283217227480b109aedc8ef (diff) | |
download | edk2-75d1a7903db171d80f9728b24274852ab613ed2b.tar.gz edk2-75d1a7903db171d80f9728b24274852ab613ed2b.tar.bz2 edk2-75d1a7903db171d80f9728b24274852ab613ed2b.zip |
OvfmPkg/VmgExitLib: Properly decode MMIO MOVZX and MOVSX opcodes
BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=3345
The MOVZX and MOVSX instructions use the ModRM byte in the instruction,
but the instruction decoding support was not decoding it. This resulted
in invalid decoding and failing of the MMIO operation. Also, when
performing the zero-extend or sign-extend operation, the memory operation
should be using the size, and not the size enumeration value.
Add the ModRM byte decoding for the MOVZX and MOVSX opcodes and use the
true data size to perform the extend operations. Additionally, add a
DEBUG statement identifying the MMIO address being flagged as encrypted
during the MMIO address validation.
Fixes: c45f678a1ea2080344e125dc55b14e4b9f98483d
Cc: Laszlo Ersek <lersek@redhat.com>
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>
Cc: Jordan Justen <jordan.l.justen@intel.com>
Cc: Brijesh Singh <brijesh.singh@amd.com>
Cc: Erdem Aktas <erdemaktas@google.com>
Cc: James Bottomley <jejb@linux.ibm.com>
Cc: Jiewen Yao <jiewen.yao@intel.com>
Cc: Min Xu <min.m.xu@intel.com>
Acked-by: Laszlo Ersek <lersek@redhat.com>
Signed-off-by: Tom Lendacky <thomas.lendacky@amd.com>
Message-Id: <5949d54cb2c9ab69256f67ed5654b32654c0501c.1619716333.git.thomas.lendacky@amd.com>
Diffstat (limited to 'MdePkg/Test')
0 files changed, 0 insertions, 0 deletions