diff options
author | Laszlo Ersek <lersek@redhat.com> | 2018-02-02 02:10:05 +0100 |
---|---|---|
committer | Laszlo Ersek <lersek@redhat.com> | 2018-04-04 16:44:18 +0200 |
commit | f0053e837a2141e3c09ad376efe27fd17c522b04 (patch) | |
tree | b3c1e4d2836e785e7f5d5c122e0938e343d58b08 /BaseTools/Source/Python/CommonDataClass/PlatformClass.py | |
parent | 351b49c1a7342bc65b6e5837458517fcd22424b0 (diff) | |
download | edk2-f0053e837a2141e3c09ad376efe27fd17c522b04.tar.gz edk2-f0053e837a2141e3c09ad376efe27fd17c522b04.tar.bz2 edk2-f0053e837a2141e3c09ad376efe27fd17c522b04.zip |
UefiCpuPkg/PiSmmCpuDxeSmm: patch "gSmmCr0" with PatchInstructionX86()
Like "gSmmCr4" in the previous patch, "gSmmCr0" is not only used for
machine code patching, but also as a means to communicate the initial CR0
value from SmmRelocateBases() to InitSmmS3ResumeState(). In other words,
the last four bytes of the "mov eax, Cr0Value" instruction's binary
representation are utilized as normal data too.
In order to get rid of the DB for "mov eax, Cr0Value", we have to split
both roles, patching and data flow. Introduce the "mSmmCr0" global (SMRAM)
variable for the data flow purpose. Rename the "gSmmCr0" variable to
"gPatchSmmCr0" so that its association with PatchInstructionX86() is clear
from the declaration, change its type to X86_ASSEMBLY_PATCH_LABEL, and
patch it with PatchInstructionX86(), to the value now contained in
"mSmmCr0".
This lets us remove the binary (DB) encoding of "mov eax, Cr0Value" in
"SmmInit.nasm".
Cc: Eric Dong <eric.dong@intel.com>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=866
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Laszlo Ersek <lersek@redhat.com>
Reviewed-by: Liming Gao <liming.gao@intel.com>
Diffstat (limited to 'BaseTools/Source/Python/CommonDataClass/PlatformClass.py')
0 files changed, 0 insertions, 0 deletions