mirror of
https://github.com/libretro/RetroArch.git
synced 2026-11-21 12:29:43 -10:00
The two CCDs of an X3D part are one performance class and within a few percent of one clock, so cpu_features_get_processor_order() put the frequency CCD first and a core pinning its emulation thread to "the strongest processor" landed on the die without the V-cache. Within a class the ranking now prefers the larger last-level cache, then the higher clock. On Linux that is cache/index3/size per processor (96M behind the V-cache CCD, 32M behind the other); on Windows the level-3 RelationCache record whose mask covers the processor, from the same GetLogicalProcessorInformation call the core list already comes from. Parts with one L3 size are unaffected. fast_cores_test: the X3D fixture with and without the cache figures, and confined to the frequency CCD.