public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
	"Dong, Guo" <guo.dong@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Dong, Eric" <eric.dong@intel.com>, "Ni, Ray" <ray.ni@intel.com>,
	"Kumar, Rahul1" <rahul1.kumar@intel.com>
Subject: Re: UefiCpuPkg/CpuDxe: Fix boot error
Date: Thu, 7 Jan 2021 10:54:49 +0100	[thread overview]
Message-ID: <d411f051-069c-2e34-a48a-b2fed5b1b04f@redhat.com> (raw)
In-Reply-To: <BL0PR11MB3236D6DA44530033211E7C4DD2AF0@BL0PR11MB3236.namprd11.prod.outlook.com>

On 01/07/21 02:00, Kinney, Michael D wrote:
> Guo,
> 
> Yes.  Using the following looks like the correct solution:
> 
> 	o64 retf

I agree; these operand size prefixes are one of the strengths of NASM.

Thanks!
Laszlo

> 
> Thanks,
> 
> Mike
> 
>> -----Original Message-----
>> From: Dong, Guo <guo.dong@intel.com>
>> Sent: Wednesday, January 6, 2021 2:07 PM
>> To: devel@edk2.groups.io; Kinney, Michael D <michael.d.kinney@intel.com>
>> Cc: Dong, Eric <eric.dong@intel.com>; Ni, Ray <ray.ni@intel.com>; lersek@redhat.com; Kumar, Rahul1
>> <rahul1.kumar@intel.com>
>> Subject: FW: UefiCpuPkg/CpuDxe: Fix boot error
>>
>>
>> Hi Mike,
>>
>> I just did a test with retfq, it looks the compiler will take 'retfq' as a label with a warnig:
>> "CpuAsm.iii:26: warning: label alone on a line without a colon might be in error"
>>
>> CpuAsm.nasm is the source file.
>> Both CpuAsm.iii and CpuAsm.obj are from the build folder.
>> CpuAsm_dasm.txt is the dasm file using objdump.
>>
>> I am using "NASM version 2.12.01rc2 compiled on Mar  7 2016".
>> BTW, if using "O64 retf" instead of "retfq", the generated obj matches with DB one.
>> Do you prefer using " O64 retf" comparing with "DB 0x48, 0xcb"?
>>
>> Thanks,
>> Guo
>>
>>> -----Original Message-----
>>> From: Kinney, Michael D <michael.d.kinney@intel.com>
>>> Sent: Tuesday, January 5, 2021 7:01 PM
>>> To: Dong, Guo <guo.dong@intel.com>; devel@edk2.groups.io; Kinney, Michael
>>> D <michael.d.kinney@intel.com>
>>> Cc: Dong, Eric <eric.dong@intel.com>; Ni, Ray <ray.ni@intel.com>;
>>> lersek@redhat.com; Kumar, Rahul1 <rahul1.kumar@intel.com>
>>> Subject: RE: [edk2-devel] [PATCH] UefiCpuPkg/CpuDxe: Fix boot error
>>>
>>> Hi Guo,
>>>
>>> Could be the port from MASM to NASM did not check to see if NASM supported
>>> the instruction.
>>>
>>> You can verify the NASM disassembly to make sure it matches the DB bytes.
>>>
>>> Mike
>>>
>>>> -----Original Message-----
>>>> From: Dong, Guo <guo.dong@intel.com>
>>>> Sent: Tuesday, January 5, 2021 4:51 PM
>>>> To: Kinney, Michael D <michael.d.kinney@intel.com>; devel@edk2.groups.io
>>>> Cc: Dong, Eric <eric.dong@intel.com>; Ni, Ray <ray.ni@intel.com>;
>>> lersek@redhat.com; Kumar, Rahul1
>>>> <rahul1.kumar@intel.com>
>>>> Subject: RE: [edk2-devel] [PATCH] UefiCpuPkg/CpuDxe: Fix boot error
>>>>
>>>>
>>>> Hi Mike,
>>>>
>>>> Thanks for the comments. I will remove DB and submit a new patch.
>>>> I used DB because retfq is used in EDK2 only in
>>> OvmfPkg\Library\LoadLinuxLib\X64\JumpToKernel.nasm and it used DB.
>>>> Not sure if there is any BKM why they use it.
>>>>
>>>> Thanks,
>>>> Guo
>>>>
>>>>> -----Original Message-----
>>>>> From: Kinney, Michael D <michael.d.kinney@intel.com>
>>>>> Sent: Monday, January 4, 2021 9:31 PM
>>>>> To: devel@edk2.groups.io; Dong, Guo <guo.dong@intel.com>; Kinney,
>>> Michael
>>>>> D <michael.d.kinney@intel.com>
>>>>> Cc: Dong, Eric <eric.dong@intel.com>; Ni, Ray <ray.ni@intel.com>;
>>>>> lersek@redhat.com; Kumar, Rahul1 <rahul1.kumar@intel.com>
>>>>> Subject: RE: [edk2-devel] [PATCH] UefiCpuPkg/CpuDxe: Fix boot error
>>>>>
>>>>> Hi Guo,
>>>>>
>>>>> NASM has good support for instructions.  Can the DB be removed and
>>> replaced
>>>>> with the equivalent instruction?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Mike
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Guo
>>> Dong
>>>>>> Sent: Thursday, December 24, 2020 12:04 PM
>>>>>> To: devel@edk2.groups.io
>>>>>> Cc: Dong, Eric <eric.dong@intel.com>; Ni, Ray <ray.ni@intel.com>;
>>>>> lersek@redhat.com; Kumar, Rahul1
>>>>>> <rahul1.kumar@intel.com>
>>>>>> Subject: [edk2-devel] [PATCH] UefiCpuPkg/CpuDxe: Fix boot error
>>>>>>
>>>>>> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3084
>>>>>>
>>>>>> When DXE drivers are dispatched above 4GB memory in 64bit
>>>>>> mode, the address setCodeSelectorLongJump in stack will
>>>>>> be override by parameter. Jump to Qword is not supported
>>>>>> by some processors. So use retfq instead.
>>>>>>
>>>>>> Signed-off-by: Guo Dong <guo.dong@intel.com>
>>>>>> ---
>>>>>>  UefiCpuPkg/CpuDxe/X64/CpuAsm.nasm | 8 +++-----
>>>>>>  1 file changed, 3 insertions(+), 5 deletions(-)
>>>>>>
>>>>>> diff --git a/UefiCpuPkg/CpuDxe/X64/CpuAsm.nasm
>>>>> b/UefiCpuPkg/CpuDxe/X64/CpuAsm.nasm
>>>>>> index c3489bcc3e..e33ddb2784 100644
>>>>>> --- a/UefiCpuPkg/CpuDxe/X64/CpuAsm.nasm
>>>>>> +++ b/UefiCpuPkg/CpuDxe/X64/CpuAsm.nasm
>>>>>> @@ -20,13 +20,11 @@
>>>>>>  ;------------------------------------------------------------------------------
>>>>>>  global ASM_PFX(SetCodeSelector)
>>>>>>  ASM_PFX(SetCodeSelector):
>>>>>> -    sub     rsp, 0x10
>>>>>> +    push    rcx,
>>>>>>      lea     rax, [setCodeSelectorLongJump]
>>>>>> -    mov     [rsp], rax
>>>>>> -    mov     [rsp+4], cx
>>>>>> -    jmp     dword far [rsp]
>>>>>> +    push    rax
>>>>>> +    DB 0x48, 0xcb                      ; retfq
>>>>>>  setCodeSelectorLongJump:
>>>>>> -    add     rsp, 0x10
>>>>>>      ret
>>>>>>
>>>>>>  ;------------------------------------------------------------------------------
>>>>>> --
>>>>>> 2.16.2.windows.1
>>>>>>
>>>>>>
>>>>>>
>>>>>> 
>>>>>>
> 


      reply	other threads:[~2021-01-07  9:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BYAPR11MB36223CE7DD008AE912112CD59ED00@BYAPR11MB3622.namprd11.prod.outlook.com>
2021-01-06 22:07 ` FW: UefiCpuPkg/CpuDxe: Fix boot error Guo Dong
2021-01-07  1:00   ` Michael D Kinney
2021-01-07  9:54     ` Laszlo Ersek [this message]

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=d411f051-069c-2e34-a48a-b2fed5b1b04f@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