On 07/12/16 13:58, Fan, Jeff wrote:
> Laszlo,
>
> I think of it. We could just remove the MtrrDebugPrintAllMtrrs() call from
> MtrrSetAllMtrrs() implementation in MtrrLib.
>
> The reason is that Aps' MTRR settings should be always same with the BPS's.
> BSP will set the MTRRs setting by MtrrSet
Laszlo,
I think of it. We could just remove the MtrrDebugPrintAllMtrrs() call from
MtrrSetAllMtrrs() implementation in MtrrLib.
The reason is that Aps' MTRR settings should be always same with the BPS's. BSP
will set the MTRRs setting by MtrrSetMemoryAttribute() or other APIs. And Aps
will alw
On 07/08/16 10:59, Fan, Jeff wrote:
> Laszlo,
>
> Thanks your feedback and provided the history on MTRRs sync code.
>
> DEBUG () running on Aps is a common issue to be avoided.
> For MtrrLib, DEBUG() is using DEBUG_CACHE for debug purpose only.
> Usually, MTRRs setting should be same between BSP/
Laszlo,
Thanks your feedback and provided the history on MTRRs sync code.
DEBUG () running on Aps is a common issue to be avoided.
For MtrrLib, DEBUG() is using DEBUG_CACHE for debug purpose only. Usually,
MTRRs setting should be same between BSP/Aps. Dump MTRRs are enough for BSP.
Maybe, we co
Jeff,
On 07/08/16 09:45, Jeff Fan wrote:
> SetMemoryAttributes() will sync BSP's MTRRs settings to all APs by
> StartupAllAPs
> service in serial mode. It may caused much performance impact if there are too
> much processors in system. This update is to invoke StartupAllAps in parallel
> mode. IA
SetMemoryAttributes() will sync BSP's MTRRs settings to all APs by StartupAllAPs
service in serial mode. It may caused much performance impact if there are too
much processors in system. This update is to invoke StartupAllAps in parallel
mode. IA32 SDM does suggest to program MTRRs in parallel mode
6 matches
Mail list logo