Lines Matching refs:microcode

175 There are some interesting situations involving CPU hotplug and microcode
178 [Please bear in mind that the kernel requests the microcode images from
186    to apply the same microcode revision to each of the CPUs.
189    and thereby in applying the correct microcode revision to it.
190    But note that the kernel does not maintain a common microcode image for the
196    In this case since we probably need to apply different microcode revisions
197    to different CPUs, the kernel maintains a copy of the correct microcode
207    (which is sent by the CPU hotplug code), the microcode update driver's
209    microcode image for that CPU.
212    doesn't have the microcode image, it does the CPU type/model discovery
213    afresh and then requests the userspace for the appropriate microcode image
216    For example, in x86, the mc_cpu_callback() function (which is the microcode
220    have a valid microcode image. This ensures that the CPU type/model
221    discovery is performed and the right microcode is applied to the CPU after
225 d. Handling microcode update during suspend/hibernate:
230    Hence, in such a case, it is not really necessary to re-apply microcode
236    powered off, during restore it becomes necessary to apply the microcode
245    the existing copy of microcode image in the kernel is not freed up.
247    kernel finds that it already has copies of the microcode images for all the
249    type/model and the need for validating whether the microcode revisions are
278     * If cpu online has not yet completed the microcode update stuff by now,
280       TASK_UNINTERRUPTIBLE state, in order to get the microcode image.