From: "Nate DeSimone" <nathaniel.l.desimone@intel.com>
To: Pedro Falcato <pedro.falcato@gmail.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Ni, Ray" <ray.ni@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [PATCH v2] PcAtChipsetPkg: Fix AcpiTimerLib incompatibility with XhciDxe
Date: Mon, 4 Dec 2023 22:13:12 +0000 [thread overview]
Message-ID: <MW4PR11MB5821877E294FD6B44AD72087CD86A@MW4PR11MB5821.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAKbZUD3WDqFhv2vfrVFTsRVoazbviMdBvUp=ZKVWqosiEXh9EQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3584 bytes --]
> -----Original Message-----
> From: Pedro Falcato <pedro.falcato@gmail.com>
> Sent: Monday, December 4, 2023 11:59 AM
> To: devel@edk2.groups.io; Desimone, Nathaniel L
> <nathaniel.l.desimone@intel.com>
> Cc: Ni, Ray <ray.ni@intel.com>; Kinney, Michael D
> <michael.d.kinney@intel.com>
> Subject: Re: [edk2-devel] [PATCH v2] PcAtChipsetPkg: Fix AcpiTimerLib
> incompatibility with XhciDxe
>
> On Mon, Dec 4, 2023 at 6:48 PM Nate DeSimone
> <nathaniel.l.desimone@intel.com<mailto:nathaniel.l.desimone@intel.com>> wrote:
> >
> > The DXE & MM standalone variant of AcpiTimerLib defines a global named
> > mPerformanceCounterFrequency. A global with an identical name is also
> > present in MdeModulePkg/Bus/Pci/XhciDxe/Xhci.c
> >
> > Since XhciDxe has a dependency on TimerLib, this can cause link errors
> > due to the same symbol being defined twice if the platform DSC chooses
> > to use AcpiTimerLib as the TimerLib implementation for any given
> > platform.
> >
> > To resolve this, I have changed made the definition of
> > mPerformanceCounterFrequency to static and renamed it to
> > mAcpiTimerLibTscFrequency. Since this variable is not used outside of
> > the DxeStandaloneMmAcpiTimerLib.c compilation unit, there is no reason
> > to have it exported as a global.
> >
> > Cc: Ray Ni <ray.ni@intel.com<mailto:ray.ni@intel.com>>
> > Cc: Michael D Kinney <michael.d.kinney@intel.com<mailto:michael.d.kinney@intel.com>>
> > Signed-off-by: Nate DeSimone <nathaniel.l.desimone@intel.com<mailto:nathaniel.l.desimone@intel.com>>
> > ---
> > .../AcpiTimerLib/DxeStandaloneMmAcpiTimerLib.c | 18
> > +++++++++---------
> > 1 file changed, 9 insertions(+), 9 deletions(-)
> >
> > diff --git
> > a/PcAtChipsetPkg/Library/AcpiTimerLib/DxeStandaloneMmAcpiTimerLib.c
> > b/PcAtChipsetPkg/Library/AcpiTimerLib/DxeStandaloneMmAcpiTimerLib.c
> > index 16ac48938f..ccceb8a649 100644
> > ---
> > a/PcAtChipsetPkg/Library/AcpiTimerLib/DxeStandaloneMmAcpiTimerLib.c
> > +++
> b/PcAtChipsetPkg/Library/AcpiTimerLib/DxeStandaloneMmAcpiTimerLib.
> > +++ c
> > @@ -1,7 +1,7 @@
> > /** @file
> > ACPI Timer implements one instance of Timer Library.
> >
> > - Copyright (c) 2013 - 2018, Intel Corporation. All rights
> > reserved.<BR>
> > + Copyright (c) 2013 - 2023, Intel Corporation. All rights
> > + reserved.<BR>
> > SPDX-License-Identifier: BSD-2-Clause-Patent
> >
> > **/
> > @@ -11,6 +11,11 @@
> > #include <Library/BaseLib.h>
> > #include <Library/HobLib.h>
> >
> > +//
> > +// Cached performance counter frequency // static UINT64
> > +mAcpiTimerLibTscFrequency = 0;
>
> I'd say you don't need to rename it if it's a static variable. Now the identifier is
> 2x longer with no additional relevant information.
This is in response to Mike K's feedback: https://edk2.groups.io/g/devel/message/111966
>
> Aren't we supposed to use STATIC vs static, CONST vs const, etc? Annoyingly
> :/
Apparently not. Honestly, I lose track of what the current coding style is sometimes too.
>
> --
> Pedro
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#112052): https://edk2.groups.io/g/devel/message/112052
Mute This Topic: https://groups.io/mt/102976788/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 8802 bytes --]
next prev parent reply other threads:[~2023-12-04 22:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 18:47 [edk2-devel] [PATCH v2] MdeModulePkg/Bus: Fix XhciDxe Linker Issues Nate DeSimone
2023-12-04 18:47 ` [edk2-devel] [PATCH v2] PcAtChipsetPkg: Fix AcpiTimerLib incompatibility with XhciDxe Nate DeSimone
2023-12-04 19:59 ` Pedro Falcato
2023-12-04 22:13 ` Nate DeSimone [this message]
2023-12-05 8:18 ` Ni, Ray
[not found] ` <179DB5683F38928F.24600@groups.io>
2023-12-06 22:50 ` Nate DeSimone
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=MW4PR11MB5821877E294FD6B44AD72087CD86A@MW4PR11MB5821.namprd11.prod.outlook.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