Re: [edk2-devel] [PATCH] MdePkg/SecPeiDxeTimerLibCpu: Better support for dynamic PcdFSBClock

2023-02-09 Thread Michael D Kinney
; From: devel@edk2.groups.io On Behalf Of joeyli via > groups.io > Sent: Thursday, February 9, 2023 5:27 PM > To: devel@edk2.groups.io; anthony.per...@citrix.com > Cc: Gao, Liming ; Liu, Zhiguang > ; Kinney, Michael D > Subject: Re: [edk2-devel] [PATCH] MdePkg/SecPeiDxeTim

Re: [edk2-devel] [PATCH] MdePkg/SecPeiDxeTimerLibCpu: Better support for dynamic PcdFSBClock

2023-02-09 Thread joeyli via groups.io
On Tue, Nov 08, 2022 at 02:31:48PM +, Anthony PERARD via groups.io wrote: > From: Anthony PERARD > > The PcdFSBClock can be a dynamic PCD. This can be an issue when > InternalX86GetTimerFrequency() tries to get the value while been > called with TPL been set to TPL_HIGH_LEVEL. > > When the

[edk2-devel] [PATCH] MdePkg/SecPeiDxeTimerLibCpu: Better support for dynamic PcdFSBClock

2022-11-08 Thread Anthony PERARD via groups.io
From: Anthony PERARD The PcdFSBClock can be a dynamic PCD. This can be an issue when InternalX86GetTimerFrequency() tries to get the value while been called with TPL been set to TPL_HIGH_LEVEL. When the PCD is dynamic, PcdGet*() calls a function that try to grab a lock which set TPL to