From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, john.e.lofgren@intel.com
Subject: Re: [edk2-devel] [Patch V3] UefiCpuPkg/CpuExceptionHandlerLib: Fix split lock
Date: Wed, 18 Sep 2019 10:52:13 +0200 [thread overview]
Message-ID: <0b464724-85d4-c8bb-d5db-c164ac51c1f5@redhat.com> (raw)
In-Reply-To: <20190917224910.28040-1-john.e.lofgren@intel.com>
On 09/18/19 00:49, John E Lofgren wrote:
> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=2150
> V3 changes:
> change to mov instruction (non locking instuction) instead
> of xchg to simplify design.
I think something's wrong -- the v3 update described above isn't
actually implemented in the patch (it continues using XCHG, rather than
MOV).
Thanks
Laszlo
>
> V2 changes:
> Add xchg 16 bit instructions to handle sgdt and sidt base
> 63:48 bits and 47:32 bits.
> Add comment to explain why xchg 64bit isnt being used
>
> Split lock happens when a locking instruction is used on mis-aligned data
> that crosses two cachelines. If close source platform enables Alignment Check
> Exception(#AC), They can hit a double fault due to split lock being in
> CpuExceptionHandlerLib.
>
> sigt and sgdt saves 10 bytes to memory, 8 bytes is base and 2 bytes is limit.
> The data is mis-aligned, can cross two cacheline, and a xchg
> instruction(locking instuction) is being utilize.
>
> Signed-off-by: John E Lofgren <john.e.lofgren@intel.com>
> ---
> UefiCpuPkg/Library/CpuExceptionHandlerLib/X64/ExceptionHandlerAsm.nasm | 20 ++++++++++++++------
> 1 file changed, 14 insertions(+), 6 deletions(-)
>
> diff --git a/UefiCpuPkg/Library/CpuExceptionHandlerLib/X64/ExceptionHandlerAsm.nasm b/UefiCpuPkg/Library/CpuExceptionHandlerLib/X64/ExceptionHandlerAsm.nasm
> index 4db1a09f28..7b7642b290 100644
> --- a/UefiCpuPkg/Library/CpuExceptionHandlerLib/X64/ExceptionHandlerAsm.nasm
> +++ b/UefiCpuPkg/Library/CpuExceptionHandlerLib/X64/ExceptionHandlerAsm.nasm
> @@ -180,21 +180,29 @@ HasErrorCode:
> push qword [rbp + 24]
>
> ;; UINT64 Gdtr[2], Idtr[2];
> + ; sidt and sgdt saves 10 bytes to memory, 8 bytes = base and 2 bytes = limit.
> + ; To avoid #AC split lock when separating base and limit into their
> + ; own separate 64 bit memory, we can’t use 64 bit xchg since base [63:48] bits
> + ; may cross the cache line.
> xor rax, rax
> push rax
> push rax
> sidt [rsp]
> - xchg rax, [rsp + 2]
> - xchg rax, [rsp]
> - xchg rax, [rsp + 8]
> + xchg eax, [rsp + 2]
> + xchg eax, [rsp]
> + xchg eax, [rsp + 8]
> + xchg ax, [rsp + 6]
> + xchg ax, [rsp + 4]
>
> xor rax, rax
> push rax
> push rax
> sgdt [rsp]
> - xchg rax, [rsp + 2]
> - xchg rax, [rsp]
> - xchg rax, [rsp + 8]
> + xchg eax, [rsp + 2]
> + xchg eax, [rsp]
> + xchg eax, [rsp + 8]
> + xchg ax, [rsp + 6]
> + xchg ax, [rsp + 4]
>
> ;; UINT64 Ldtr, Tr;
> xor rax, rax
>
next prev parent reply other threads:[~2019-09-18 8:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 22:49 [Patch V3] UefiCpuPkg/CpuExceptionHandlerLib: Fix split lock John E Lofgren
2019-09-18 8:52 ` Laszlo Ersek [this message]
2019-09-18 15:23 ` [edk2-devel] " John E Lofgren
-- strict thread matches above, loose matches on Subject: below --
2019-09-18 15:43 John E Lofgren
2019-09-18 17:57 ` [edk2-devel] " Laszlo Ersek
2019-09-20 6:39 ` Dong, Eric
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=0b464724-85d4-c8bb-d5db-c164ac51c1f5@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