Hey Dimitri, Can you expand on what problems/situations where you're actually seeing late loading be a solution?
The reason I ask is that every communication I've had with Intel has indicated that late loading is risky and should not be used. The reason for this is that performing late loading on a running system can result in race conditions where cpu cores have different values for MSRs/cpu flags, or even have them disappear momentarily while the microcode is loading. This can cause a variety of problems for virtual machine hosts/hypervisors. Also this statement: "For example, from time to time, certain microcode updates are pulled or get blacklisted from late loading." isn't really a reason to do late loading. Finally, why is this being done via tmpfiles.d(5)? If we're really going to do this, should it not be its own systemd unit, rather than hijacking something that isn't related? Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862938 Title: Enable late loading of microcode by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1862938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
