From: "Laszlo Ersek" <lersek@redhat.com>
To: "Duran, Leo" <leo.duran@amd.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"eric.dong@intel.com" <eric.dong@intel.com>
Cc: "Ni, Ray" <ray.ni@intel.com>
Subject: Re: [edk2-devel] [PATCH 1/2] UefiCpuPkg: LocalApicLib: Export StandardSignatureIsAuthenticAMD function
Date: Wed, 26 Feb 2020 17:19:02 +0100 [thread overview]
Message-ID: <bf9758ee-fd36-1e98-d86a-f4ab00e9068f@redhat.com> (raw)
In-Reply-To: <BN6PR12MB19229C907497DDD231D3BC26F9EA0@BN6PR12MB1922.namprd12.prod.outlook.com>
On 02/26/20 16:03, Duran, Leo wrote:
>
>
>> -----Original Message-----
>> From: Laszlo Ersek [mailto:lersek@redhat.com]
>> Sent: Wednesday, February 26, 2020 5:13 AM
>> To: devel@edk2.groups.io; eric.dong@intel.com; Duran, Leo
>> <leo.duran@amd.com>
>> Cc: Ni, Ray <ray.ni@intel.com>
>> Subject: Re: [edk2-devel] [PATCH 1/2] UefiCpuPkg: LocalApicLib: Export
>> StandardSignatureIsAuthenticAMD function
>>
>> On 02/26/20 06:05, Dong, Eric wrote:
>>> Hi Leo,
>>>
>>> Yes, I means you also change the cod position in the c file, so in the patch
>> file, it seems like it has other changes.
>>> My recommendation is to refine the patch to not change the code postion.
>>
>> Indeed I noticed that too. I figured this change -- moving the code around,
>> beyond purely making it public -- was intentional. I assumed the new position
>> of the function within the source code made more sense to Leo.
> [Duran, Leo] You're exactly right, Laszlo, let me explain:
>
> The function was moved down because the top spots are reserved for internal functions, according to this comment in the source::
> //
> // Library internal functions
> //
>
> In this case, there were two internal (local) functions at the top of the file:
> BOOLEAN
> StandardSignatureIsAuthenticAMD (
> VOID
> )
> {
> }
>
> BOOLEAN
> LocalApicBaseAddressMsrSupported (
> VOID
> )
> {
> }
>
> So I moved them like this:
> BOOLEAN
> LocalApicBaseAddressMsrSupported (
> VOID
> )
> {
> }
>
> BOOLEAN
> EFIAPI
> StandardSignatureIsAuthenticAMD (
> VOID
> )
> {
> }
>
> Other functions that follow are external functions, using the EFIAPI prefix.
> Leo.
makes sense, thanks.
Laszlo
next prev parent reply other threads:[~2020-02-26 16:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 19:39 [PATCH 0/2] UefiCpuPkg/Library: Fix bug in MpInitLib Leo Duran
2020-02-25 19:39 ` [PATCH 1/2] UefiCpuPkg: LocalApicLib: Export StandardSignatureIsAuthenticAMD function Leo Duran
2020-02-26 1:13 ` Dong, Eric
2020-02-26 2:41 ` Duran, Leo
2020-02-26 5:05 ` Dong, Eric
2020-02-26 10:13 ` [edk2-devel] " Laszlo Ersek
2020-02-26 15:03 ` Duran, Leo
2020-02-26 16:19 ` Laszlo Ersek [this message]
2020-02-26 15:59 ` Duran, Leo
2020-02-25 19:39 ` [PATCH 2/2] UefiCpuPkg: MpInitLib: Exclude code no pertinent to AMD processors Leo Duran
2020-02-26 7:45 ` Ni, Ray
2020-02-26 7:56 ` Siyuan, Fu
2020-02-26 0:54 ` [edk2-devel] [PATCH 0/2] UefiCpuPkg/Library: Fix bug in MpInitLib Laszlo Ersek
2020-02-26 7:57 ` Ni, Ray
2020-02-26 8:56 ` Liming Gao
2020-02-26 15:11 ` Duran, Leo
2020-02-26 16:24 ` Laszlo Ersek
2020-02-26 16:35 ` Duran, Leo
2020-02-26 15:25 ` Duran, Leo
2020-02-26 15:46 ` Duran, Leo
2020-02-26 16:20 ` Laszlo Ersek
2020-02-26 16:39 ` Duran, Leo
2020-02-26 16:46 ` Duran, Leo
2020-02-26 17:45 ` Laszlo Ersek
2020-02-26 17:51 ` Duran, Leo
2020-02-27 5:55 ` Ni, Ray
2020-02-27 18:17 ` Duran, Leo
2020-02-28 6:47 ` Ni, Ray
2020-02-28 16:38 ` Duran, Leo
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=bf9758ee-fd36-1e98-d86a-f4ab00e9068f@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