Microcode update system

1. A method for updating microcode, comprising:

receiving, by a microcode update engine provided via operation of a processing system in a computing device and without receiving an initialization engine code update for initialization engine code that is stored in a code region of at least one initialization memory device in the computing device and that is configured to provide an initialization engine, a microcode update for existing microcode that is included in the initialization engine code;

writing, by the microcode update engine, the microcode update to a Unified Extensible Firmware Interface (UEFI) variable in a data region of the at least one initialization memory device that stores data utilized by the initialization engine during computing device initialization operations and computing device runtime operations;

beginning, by the microcode update engine subsequent to writing the microcode update to the data region of the at least one memory device and utilizing the initialization engine provided by the initialization engine code that is stored in the code region of the at least one initialization memory device and that includes the existing microcode, computing device initialization operations;

identifying, by the microcode update engine during a microcode update portion of the computing device initialization operations, the microcode update in the data region of the at least one initialization memory device;

performing, by the microcode update engine, microcode update operations using the microcode update in the data region of the at least one initialization memory device; and

completing, by the microcode update engine, the computing device initialization operations utilizing the initialization engine provided by the initialization engine code, and the microcode update in place of the existing microcode included in the initialization engine code.

2. The method of claim 1 , further comprising:

determining, by the microcode update engine in response to identifying the microcode update in the data region of the at least one initialization memory device, whether the microcode update should be applied in place of the existing microcode included in the initialization engine code; and

performing, by the microcode update engine using the microcode update and in response to determining that the microcode update should be applied in place of the existing microcode included in the initialization engine code, any of a subset of the computing device initialization operations that have not yet been performed.

3. The method of claim 2 , further comprising:

performing, by the microcode update engine in response to determining that the microcode update should not be applied in place of the existing microcode included in the initialization engine code, the initialization operations using the existing microcode included in the initialization engine code.

4. The method of claim 1 , further comprising:

validating, by the microcode update engine prior to performing the microcode update operations using the microcode update in the data region of the at least one initialization memory device, the microcode update.

5. The method of claim 4 , further comprising:

erasing, by the microcode update engine in response to a failure in validating the microcode update, the microcode update from the UEFI variable in the data region of the at least one initialization memory device.

6. The method of claim 1 , wherein the beginning the computing device initialization operations include copying the initialization engine code to a main memory system, and wherein the microcode update operations include copying the microcode update to the main memory system.

7. An Information Handling System (IHS), comprising:

a processing system that includes at least one hardware processor that is configured to execute instructions that cause the processing system to provide a microcode update engine that is configured to:

receive, without receiving an initialization engine code update for initialization engine code that is stored in a code region of at least one initialization memory device and that is configured to provide an initialization engine, a microcode update for existing microcode that is included in the initialization engine code;

write the microcode update to a Unified Extensible Firmware Interface (UEFI) variable in a data region of the at least one initialization memory device that stores data utilized by the initialization engine during computing device initialization operations and computing device runtime operations;

begin, subsequent to writing the microcode update to the data region of the at least one memory device and utilizing the initialization engine provided by the initialization engine code that is stored in the code region of the at least one initialization memory device and that includes the existing microcode, computing device initialization operations;

identify, during a microcode update portion of the computing device initialization operations, the microcode update in the data region of the at least one initialization memory device;

perform microcode update operations using the microcode update in the data region of the at least one initialization memory device; and

complete the computing device initialization operations utilizing the initialization engine provided by the initialization engine code, and the microcode update in place of the existing microcode included in the initialization engine code.

8. The IHS of claim 7 , wherein the microcode update engine is configured to:

determine, in response to identifying the microcode update in the data region of the at least one initialization memory device, whether the microcode update should be applied in place of the existing microcode included in the initialization engine code; and

perform, using the microcode update and in response to determining that the microcode update should be applied in place of the existing microcode included in the initialization engine code, any of a subset of the computing device initialization operations that have not yet been performed.

9. The IHS of claim 8 , wherein the microcode update engine is configured to:

perform, in response to determining that the microcode update should not be applied in place of the existing microcode included in the initialization engine code, the microcode update operations using the existing microcode included in the initialization engine code.

10. The IHS of claim 7 , wherein the microcode update engine is configured to:

validate, prior to performing the microcode update operations using the microcode update in the data region of the at least one initialization memory device, the microcode update.

11. The IHS of claim 10 , wherein the microcode update engine is configured to:

erase, in response to a failure in validating the microcode update, the microcode update from the UEFI variable in the data region of the at least one initialization memory device.

12. The IHS of claim 7 , wherein the beginning the computing device initialization operations include copying the initialization engine code to a main memory system, and wherein the microcode update operations include copying the microcode update to the main memory system.