For the great majority of Mac users, M1 series Macs are a big step forward. But some users want the impossible. What can’t M1 Macs do?
M1 Max
Fixes a bug which could incorrectly report the SSV was disabled on M1 Macs, and improves reporting of M1 Platform Security on non-English systems.
Improves reporting of results on T2 and M1 Macs, and clarifies old versions of Gatekeeper seen on newer Macs. Recommended for all users.
From the anatomy of the CPU cores, to the queues of threads in GCD, and assignment to a core cluster, this details how threads are managed for the M1 series chips.
Why can’t the taskpolicy command tool be used to promote software to be able to run on the M1 chip’s Performance cores? Does it change QoS?
Is it overhead from sandboxing, the file system, the throttling of I/O, or the limitations of the Efficiency cores? Is there anything a user can do?
According to macOS Help, safe mode stops some software from loading, and performs a check of the startup disk. Here’s a more detailed and accurate account of what it does.
Metal provides low-level access to 3D graphics, rendering and compute features in GPUs. With the deprecation of OpenGL and OpenCL, it’s vital, especially for M1 Macs/
An accessible summary of the CPU cores in M1 chips, and how they appear to be managed by macOS to get the best for different classes of process.
Results from running 10-70 identical compute-intensive processes on M1 chips shows the differences in strategy between background and high priority settings.
The Eclectic Light Company 