如果是hw或者istat检测不出来 这是
Vit9696 原话:
Check smcread -s, you will find the temperature for all your cores properly listed. See the key names here:
https://github.com/acidanthera/VirtualSMC/blob/master/Docs/SMCKeys.txt#L847
If it is not the case, well, I can explore it with you, but this is unlikely. Tt was well tested, and VSMC supports up to 36 cores (Apple max, due to alphabet limitations).
Relevant FAQ entries explaining why some software is broken (nobody reads docs, I get it):
https://github.com/acidanthera/VirtualSMC/blob/master/Docs/FAQ.md#why-does-sensor-x-not-show-the-information-in-y
https://github.com/acidanthera/VirtualSMC/blob/master/Docs/SensorInfo.md#recommendations
In short, iStat Menus provides a custom profile (FauxMac) when it detects FakeSMC, which creates and uses SMC keys not existent on a real mac:
https://github.com/acidanthera/VirtualSMC/blob/master/Docs/iStat.txt#L1953
This is not the case for VirtualSMC, and VirtualSMC will not invent its own keys but only use the ones found on a real mac. iStat Menus thinks that a hack running vsmc is a real mac, and for this reason the corresponding profiles of each mac model are used (each profile is listed in the document above). Different mac models have different sensor list and different limitations (e.g. core count). That means, iStat Menus will not *try* to read more SMC keys than it expects to find in a corresponding mac model.
This behaviour is nothing but a bug of iStat Menus, as even on a real mac the CPU can be upgraded with more cores, and depending on the firmware/software more keys could appear (especially on T2). One could also use VirtualSMC to provide more keys on a real mac. If you find it uncomfortable, you should consider writing your own monitoring software or bugreporting iStat Menus author suggesting to:
— remove the "count" limitations
— allow custom sensor profile creation
This is the most reasonable decision.
Also, while it may surprise you, but the values CPUSensors report are actually wrong on systems with multiple CPUs, and I strongly doubt the core values are correct everywhere as well (due to wrong topology/ht analysis) ;)
Hope it helps and answers all the questions. Really, docs are your friend, it is no fun to write things twice.