# Explain BIOS and UEFI Firmware Mechanisms Answer the following firmware and low-level systems questions. State assumptions about architecture and firmware mode rather than presenting one platform-specific path as universal. ### Part 1: System Management Interrupts Explain what a System Management Interrupt is, how it transfers control to firmware, what System Management Mode is used for, and why excessive or unsafe SMI handling can harm correctness or latency. #### What This Part Should Cover ```premium-lock What This Part Should Cover ``` ### Part 2: Reliability, Availability, and Serviceability Explain how a platform detects, contains, reports, and sometimes corrects hardware faults. Include memory error correction and the path from hardware or firmware reporting to the operating system. #### What This Part Should Cover ```premium-lock What This Part Should Cover ``` ### Part 3: Memory Initialization Walk through the major goals of early memory initialization before normal operating-system execution. #### What This Part Should Cover ```premium-lock What This Part Should Cover ``` ### Part 4: Finding ACPI Tables Explain how an operating system locates the ACPI root data structure and follows it to other tables, including validation and the difference between legacy BIOS and UEFI discovery paths. #### What This Part Should Cover ```premium-lock What This Part Should Cover ``` ### What a Strong Answer Covers ```premium-lock What a Strong Answer Covers ``` ### Follow-up Questions - How would you debug a long-tail latency spike caused by firmware? - What can go wrong when firmware publishes incorrect memory maps? - How do corrected-error rates inform predictive maintenance?