From: Laszlo Ersek <lersek@redhat.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
edk2-devel-01 <edk2-devel@lists.01.org>
Cc: "Ni, Ruiyu" <ruiyu.ni@intel.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
"Dong, Eric" <eric.dong@intel.com>
Subject: Re: [PATCH 1/3] UefiCpuPkg/PiSmmCpuDxeSmm: update comments in IA32 SmmStartup()
Date: Tue, 30 Jan 2018 22:55:53 +0100 [thread overview]
Message-ID: <f3385eec-a80d-30d0-7d76-910fa04d27b8@redhat.com> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5B895B7E9@ORSMSX113.amr.corp.intel.com>
On 01/30/18 22:26, Kinney, Michael D wrote:
> Laszlo,
>
> Maybe we can add a macro to help:
>
> #define PATCH_X86_ASM(Label,Type,Value) *((Type *)(&Label) - 1) = (Type)(Value)
>
> PATCH_X86_ASM (gSmmCr0, UINT32, AsmReadCr0());
Before sending my previous email, I thought of something like this. Here
I slightly dislike:
- the unaligned access to a wider-than-byte object
- the larger potential for triggering undefined behavior in the C
language implementation (due to type punning) -- doing the arithmetic
in UINTN and using CopyMem for the data movement should mitigate that
- the requirement that the object to patch has to be followed by the
same number of bytes (otherwise linking might fail, I think). For
example if we'd like to patch 4 bytes at the very end of the assembly
code, e.g. in a jmp instruction, we'd have to match that with a DD,
just so the extern UINT32 global variable could be declared and
linked. I think requiring just one byte trailing padding and making
all such markers UINT8 is easier to handle
- the requirement that the declared type of "gSmmCr0" match the type
passed to the macro as 2nd argument
That said, I'm fine using either of PATCH_X86_ASM() and PatchAssembly().
Thanks!
Laszlo
>
> Mike
>
>> -----Original Message-----
>> From: Kinney, Michael D
>> Sent: Tuesday, January 30, 2018 12:31 PM
>> To: Laszlo Ersek <lersek@redhat.com>; edk2-devel-01
>> <edk2-devel@lists.01.org>; Kinney, Michael D
>> <michael.d.kinney@intel.com>
>> Cc: Ni, Ruiyu <ruiyu.ni@intel.com>; Paolo Bonzini
>> <pbonzini@redhat.com>; Yao, Jiewen
>> <jiewen.yao@intel.com>; Dong, Eric <eric.dong@intel.com>
>> Subject: RE: [edk2] [PATCH 1/3]
>> UefiCpuPkg/PiSmmCpuDxeSmm: update comments in IA32
>> SmmStartup()
>>
>> Laszlo,
>>
>> We have already used this technique in other NASM files
>> to remove DBs.
>>
>> Let us know if you have suggestions on how to make the
>> C code that performs the patches easier to read and
>> maintain.
>>
>> Mike
>>
>>> -----Original Message-----
>>> From: edk2-devel [mailto:edk2-devel-
>> bounces@lists.01.org]
>>> On Behalf Of Laszlo Ersek
>>> Sent: Tuesday, January 30, 2018 10:17 AM
>>> To: Kinney, Michael D <michael.d.kinney@intel.com>;
>> edk2-
>>> devel-01 <edk2-devel@lists.01.org>
>>> Cc: Ni, Ruiyu <ruiyu.ni@intel.com>; Paolo Bonzini
>>> <pbonzini@redhat.com>; Yao, Jiewen
>>> <jiewen.yao@intel.com>; Dong, Eric
>> <eric.dong@intel.com>
>>> Subject: Re: [edk2] [PATCH 1/3]
>>> UefiCpuPkg/PiSmmCpuDxeSmm: update comments in IA32
>>> SmmStartup()
>>>
>>> On 01/30/18 18:22, Kinney, Michael D wrote:
>>>> Laszlo,
>>>>
>>>> The DBs can be removed if the label is moved after
>>>> the instruction and the patch is done to the label
>>>> minus the size of the patch value.
>>>
>>> Indeed I haven't thought of this.
>>>
>>> If I understand correctly, it means
>>>
>>> extern UINT8 gSmmCr0;
>>>
>>> *(UINT32*)(&gSmmCr0 - sizeof (UINT32)) =
>>> (UINT32)AsmReadCr0 ();
>>>
>>> TBH, the DB feels less ugly to me than this :)
>>>
>>> Still, if you think it would be an acceptable price to
>>> pay for removing
>>> the remaining DBs, I can respin.
>>>
>>> Thanks
>>> Laszlo
>>>
>>>>> -----Original Message-----
>>>>> From: edk2-devel [mailto:edk2-devel-
>>> bounces@lists.01.org]
>>>>> On Behalf Of Laszlo Ersek
>>>>> Sent: Tuesday, January 30, 2018 7:34 AM
>>>>> To: edk2-devel-01 <edk2-devel@lists.01.org>
>>>>> Cc: Ni, Ruiyu <ruiyu.ni@intel.com>; Yao, Jiewen
>>>>> <jiewen.yao@intel.com>; Dong, Eric
>>> <eric.dong@intel.com>;
>>>>> Paolo Bonzini <pbonzini@redhat.com>
>>>>> Subject: [edk2] [PATCH 1/3]
>> UefiCpuPkg/PiSmmCpuDxeSmm:
>>>>> update comments in IA32 SmmStartup()
>>>>>
>>>>> The gSmmCr3, gSmmCr4, gSmmCr0 and gSmmJmpAddr global
>>>>> variables are used
>>>>> for patching assembly instructions, thus we can
>> never
>>>>> remove the DB
>>>>> encodings for those instructions. At least we should
>>> add
>>>>> the intended
>>>>> meanings in comments.
>>>>>
>>>>> This patch only changes comments.
>>>>>
>>>>> Cc: Eric Dong <eric.dong@intel.com>
>>>>> Cc: Jian J Wang <jian.j.wang@intel.com>
>>>>> Cc: Jiewen Yao <jiewen.yao@intel.com>
>>>>> Cc: Paolo Bonzini <pbonzini@redhat.com>
>>>>> Cc: Ruiyu Ni <ruiyu.ni@intel.com>
>>>>> Contributed-under: TianoCore Contribution Agreement
>>> 1.1
>>>>> Signed-off-by: Laszlo Ersek <lersek@redhat.com>
>>>>> ---
>>>>> UefiCpuPkg/PiSmmCpuDxeSmm/Ia32/SmmInit.nasm | 8
>> ++++-
>>> ---
>>>>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>>>>
>>>>> diff --git
>>> a/UefiCpuPkg/PiSmmCpuDxeSmm/Ia32/SmmInit.nasm
>>>>> b/UefiCpuPkg/PiSmmCpuDxeSmm/Ia32/SmmInit.nasm
>>>>> index e96dd8d2392a..08534dba64b7 100644
>>>>> --- a/UefiCpuPkg/PiSmmCpuDxeSmm/Ia32/SmmInit.nasm
>>>>> +++ b/UefiCpuPkg/PiSmmCpuDxeSmm/Ia32/SmmInit.nasm
>>>>> @@ -44,34 +44,34 @@ global ASM_PFX(SmmStartup)
>>>>> ASM_PFX(SmmStartup):
>>>>> DB 0x66
>>>>> mov eax, 0x80000001 ; read
>>>>> capability
>>>>> cpuid
>>>>> DB 0x66
>>>>> mov ebx, edx ; rdmsr
>> will
>>>>> change edx. keep it in ebx.
>>>>> - DB 0x66, 0xb8
>>>>> + DB 0x66, 0xb8 ; mov eax,
>>> imm32
>>>>> ASM_PFX(gSmmCr3): DD 0
>>>>> mov cr3, eax
>>>>> DB 0x67, 0x66
>>>>> lgdt [cs:ebp + (ASM_PFX(gcSmiInitGdtr) -
>>>>> ASM_PFX(SmmStartup))]
>>>>> - DB 0x66, 0xb8
>>>>> + DB 0x66, 0xb8 ; mov eax,
>>> imm32
>>>>> ASM_PFX(gSmmCr4): DD 0
>>>>> mov cr4, eax
>>>>> DB 0x66
>>>>> mov ecx, 0xc0000080 ; IA32_EFER
>>> MSR
>>>>> rdmsr
>>>>> DB 0x66
>>>>> test ebx, BIT20 ; check NXE
>>>>> capability
>>>>> jz .1
>>>>> or ah, BIT3 ; set NXE
>> bit
>>>>> wrmsr
>>>>> .1:
>>>>> - DB 0x66, 0xb8
>>>>> + DB 0x66, 0xb8 ; mov eax,
>>> imm32
>>>>> ASM_PFX(gSmmCr0): DD 0
>>>>> DB 0xbf, PROTECT_MODE_DS, 0 ; mov di,
>>>>> PROTECT_MODE_DS
>>>>> mov cr0, eax
>>>>> - DB 0x66, 0xea ; jmp far
>>>>> [ptr48]
>>>>> + DB 0x66, 0xea ; jmp far
>>>>> [ptr48]
>>>>> ASM_PFX(gSmmJmpAddr):
>>>>> DD @32bit
>>>>> DW PROTECT_MODE_CS
>>>>> @32bit:
>>>>> mov ds, edi
>>>>> mov es, edi
>>>>> --
>>>>> 2.14.1.3.gb7cf6e02401b
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> edk2-devel mailing list
>>>>> edk2-devel@lists.01.org
>>>>> https://lists.01.org/mailman/listinfo/edk2-devel
>>>
>>> _______________________________________________
>>> edk2-devel mailing list
>>> edk2-devel@lists.01.org
>>> https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2018-01-30 21:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 15:33 [PATCH 0/3] UefiCpuPkg/PiSmmCpuDxeSmm: fix IA32 SmmStartup() regression on KVM Laszlo Ersek
2018-01-30 15:33 ` [PATCH 1/3] UefiCpuPkg/PiSmmCpuDxeSmm: update comments in IA32 SmmStartup() Laszlo Ersek
2018-01-30 17:22 ` Kinney, Michael D
2018-01-30 18:17 ` Laszlo Ersek
2018-01-30 20:31 ` Kinney, Michael D
2018-01-30 21:26 ` Kinney, Michael D
2018-01-30 21:55 ` Laszlo Ersek [this message]
2018-01-30 21:45 ` Laszlo Ersek
2018-01-30 22:25 ` Kinney, Michael D
2018-01-31 5:44 ` Ni, Ruiyu
2018-01-31 5:54 ` Ni, Ruiyu
2018-01-31 10:56 ` Laszlo Ersek
2018-01-31 10:42 ` Laszlo Ersek
2018-01-31 10:40 ` Laszlo Ersek
2018-01-31 22:11 ` Kinney, Michael D
2018-02-02 6:05 ` Laszlo Ersek
2018-02-02 10:06 ` Ard Biesheuvel
2018-02-02 13:26 ` Laszlo Ersek
2018-02-02 13:28 ` Leif Lindholm
2018-02-02 13:36 ` Laszlo Ersek
2018-01-30 15:33 ` [PATCH 2/3] UefiCpuPkg/PiSmmCpuDxeSmm: remove unneeded DBs from " Laszlo Ersek
2018-01-31 5:45 ` Ni, Ruiyu
2018-01-30 15:33 ` [PATCH 3/3] UefiCpuPkg/PiSmmCpuDxeSmm: eliminate conditional jump in " Laszlo Ersek
2018-01-31 5:12 ` Ni, Ruiyu
2018-01-30 16:37 ` [PATCH 0/3] UefiCpuPkg/PiSmmCpuDxeSmm: fix IA32 SmmStartup() regression on KVM Paolo Bonzini
2018-01-31 12:17 ` Laszlo Ersek
2018-02-01 1:20 ` Wang, Jian J
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=f3385eec-a80d-30d0-7d76-910fa04d27b8@redhat.com \
--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