public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gao, Liming" <liming.gao@intel.com>
To: "Fan, Jeff" <jeff.fan@intel.com>,
	"edk2-devel@ml01.01.org" <edk2-devel@ml01.01.org>
Cc: "Tian, Feng" <feng.tian@intel.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [PATCH] UefiCpuPkg/ExceptionHandlerAsm.S: Fix code length issue with GCC 5.4
Date: Tue, 21 Feb 2017 04:37:11 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14D6E1370@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <20170221033222.26496-1-jeff.fan@intel.com>

Reviewed-by: Liming Gao <liming.gao@intel.com>

>-----Original Message-----
>From: Fan, Jeff
>Sent: Tuesday, February 21, 2017 11:32 AM
>To: edk2-devel@ml01.01.org
>Cc: Gao, Liming <liming.gao@intel.com>; Tian, Feng <feng.tian@intel.com>;
>Kinney, Michael D <michael.d.kinney@intel.com>
>Subject: [PATCH] UefiCpuPkg/ExceptionHandlerAsm.S: Fix code length issue
>with GCC 5.4
>
>X64\ExceptionHandlerAsm.S define MARCO to set up 32 IDT entries header.
>It assume GCC compiler will generate the same code length on the following
>instrction for each IDT entry.
>  jmp    ASM_PFX(CommonInterruptEntry)
>
>It works with GCC 4.x. However, GCC 5.4 will generate different code size of
>IDT
>entry code per the offset value from CommonInterruptEntry address. We
>should use
>DB to make sure each IDT entry header has the same size whatever compiler
>version.
>
>.ASM and .nasm used the different solution and do not have this issue.
>
>https://bugzilla.tianocore.org/show_bug.cgi?id=389
>
>Cc: Liming Gao <liming.gao@intel.com>
>Cc: Feng Tian <feng.tian@intel.com>
>Cc: Michael D Kinney <michael.d.kinney@intel.com>
>Contributed-under: TianoCore Contribution Agreement 1.0
>Signed-off-by: Jeff Fan <jeff.fan@intel.com>
>---
> UefiCpuPkg/Library/CpuExceptionHandlerLib/X64/ExceptionHandlerAsm.S |
>5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
>diff --git
>a/UefiCpuPkg/Library/CpuExceptionHandlerLib/X64/ExceptionHandlerAsm.S
>b/UefiCpuPkg/Library/CpuExceptionHandlerLib/X64/ExceptionHandlerAsm.S
>index 6b62f09..975adaa 100644
>---
>a/UefiCpuPkg/Library/CpuExceptionHandlerLib/X64/ExceptionHandlerAsm.S
>+++
>b/UefiCpuPkg/Library/CpuExceptionHandlerLib/X64/ExceptionHandlerAsm.S
>@@ -1,5 +1,5 @@
> #------------------------------------------------------------------------------ ;
>-# Copyright (c) 2012 - 2014, Intel Corporation. All rights reserved.<BR>
>+# Copyright (c) 2012 - 2017, Intel Corporation. All rights reserved.<BR>
> # This program and the accompanying materials
> # are licensed and made available under the terms and conditions of the BSD
>License
> # which accompanies this distribution.  The full text of the license may be
>found at
>@@ -36,7 +36,8 @@ ASM_GLOBAL ASM_PFX(CommonExceptionHandler)
> .macro IDT_MACRO arg
>   push    \arg
> #endif
>-  jmp    ASM_PFX(CommonInterruptEntry)
>+  .byte   0xe9      # jmp     ASM_PFX(CommonInterruptEntry)
>+  .long   ASM_PFX(CommonInterruptEntry) - . - 4
> .endm
>
> AsmIdtVectorBegin:
>--
>2.9.3.windows.2



      reply	other threads:[~2017-02-21  4:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-21  3:32 [PATCH] UefiCpuPkg/ExceptionHandlerAsm.S: Fix code length issue with GCC 5.4 Jeff Fan
2017-02-21  4:37 ` Gao, Liming [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=4A89E2EF3DFEDB4C8BFDE51014F606A14D6E1370@shsmsx102.ccr.corp.intel.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