Lines Matching refs:microcode

176 There are some interesting situations involving CPU hotplug and microcode
179 [Please bear in mind that the kernel requests the microcode images from
187    to apply the same microcode revision to each of the CPUs.
190    and thereby in applying the correct microcode revision to it.
191    But note that the kernel does not maintain a common microcode image for the
197    In this case since we probably need to apply different microcode revisions
198    to different CPUs, the kernel maintains a copy of the correct microcode
208    (which is sent by the CPU hotplug code), the microcode update driver's
210    microcode image for that CPU.
213    doesn't have the microcode image, it does the CPU type/model discovery
214    afresh and then requests the userspace for the appropriate microcode image
217    For example, in x86, the mc_cpu_callback() function (which is the microcode
221    have a valid microcode image. This ensures that the CPU type/model
222    discovery is performed and the right microcode is applied to the CPU after
226 d. Handling microcode update during suspend/hibernate:
231    Hence, in such a case, it is not really necessary to re-apply microcode
237    powered off, during restore it becomes necessary to apply the microcode
246    the existing copy of microcode image in the kernel is not freed up.
248    kernel finds that it already has copies of the microcode images for all the
250    type/model and the need for validating whether the microcode revisions are
279     * If cpu online has not yet completed the microcode update stuff by now,
281       TASK_UNINTERRUPTIBLE state, in order to get the microcode image.