You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On some platforms like Intel before Skylake, Intel Xeon W/Scalable, and AMD we use ACPI PM timer to determine CPU frequency. This is done by OcTimerLib in its constructor to provide timer interface in our code.
As a result currently any binary referencing OcTimerLib directly or indirectly (e.g. via OcBootManagementLib) may get a ~100 ms delay during startup.
OpenCore itself needs OcTimerLib and the calculation, but we may not want to calculate the ACPI PM frequency in RELEASE builds on platforms that do not need it (desktop and server Skylake+), this is still an issue.
Other software like third-party GUI will need to reference OcBootManagementLib, and for that we want to make OcTimerLib do its job only once by installing a protocol or a volatile UEFI variable.
The text was updated successfully, but these errors were encountered:
The contents of OC_CPU_INFO are implicitly related (i.e. now it may store several frequency, i.e. CPUFrequency based on ART and ACPU PM). Should it just be stripped to the minimum used by dependencies such as the SMBIOS code?
On some platforms like Intel before Skylake, Intel Xeon W/Scalable, and AMD we use ACPI PM timer to determine CPU frequency. This is done by OcTimerLib in its constructor to provide timer interface in our code.
As a result currently any binary referencing OcTimerLib directly or indirectly (e.g. via OcBootManagementLib) may get a ~100 ms delay during startup.
The text was updated successfully, but these errors were encountered: