Multi-tenant firmware and hardware update exchange using BDAT schema
An information handling system may include at least one processor, a Basic Input/Output System (BIOS), a physical information handling resource, and a computer-readable medium having instructions thereon that are executable by the at least one processor for: executing an operating system (OS) that includes a BIOS Data Advanced Configuration and Power Interface (ACPI) Table (BDAT) driver; executing at least one virtual machine (VM) that includes a virtual BDAT driver; detecting an event notification generated by the physical information handling resource; and transmitting, to the VM, information regarding the event notification via the BDAT driver and the virtual BDAT driver.
1. An information handling system comprising:
at least one processor;
a Basic Input/Output System (BIOS);
a physical information handling resource; and
a computer-readable medium having instructions thereon that are executable by the at least one processor for:
executing an operating system (OS) that includes a BIOS Data Advanced Configuration and Power Interface (ACPI) Table (BDAT) driver;
executing at least one virtual machine (VM) that includes a virtual BDAT driver;
detecting an event notification generated by the physical information handling resource; and
transmitting, to the VM, information regarding the event notification via the BDAT driver and the virtual BDAT driver, wherein the transmitting includes transmitting the information according to a vendor-specific BDAT schema via a secure reserved memory region of a memory map of the information handling system by:
the BDAT driver querying the information handling system to retrieve a key associated with the secure reserved memory region;
the BDAT driver transmitting the key to the virtual BDAT driver of the VM; and
the VM accessing the secure reserved memory region with the key.
2. The information handling system of claim 1 , wherein the information handling system is configured to execute a plurality of VMs each including a respective virtual BDAT driver.
3. The information handling system of claim 1 , wherein the BIOS is a Unified Extensible Firmware Interface (UEFI) BIOS.
4. The information handling system of claim 1 , wherein the BDAT driver is configured to communicate with the physical information handling resource via Windows Management Instrumentation (WMI).
5. The information handling system of claim 1 , wherein the BDAT driver is a vendor-specific BDAT driver.
6. A method comprising:
executing, at an information handling system that includes a Basic Input/Output System (BIOS) and a physical information handling resource, an operating system (OS) that includes a BIOS Data Advanced Configuration and Power Interface (ACPI) Table (BDAT) driver;
executing, at the information handling system, at least one virtual machine (VM) that includes a virtual BDAT driver;
detecting, at the information handling system, an event notification generated by the physical information handling resource; and
transmitting, from the information handling system and to the VM, information regarding the event notification via the BDAT driver and the virtual BDAT driver, wherein the transmitting includes transmitting the information according to a vendor-specific BDAT schema via a secure reserved memory region of a memory map of the information handling system by:
the BDAT driver querying the information handling system to retrieve a key associated with the secure reserved memory region;
the BDAT driver transmitting the key to the virtual BDAT driver of the VM; and
the VM accessing the secure reserved memory region with the key.
7. The method of claim 6 , further comprising executing a plurality of VMs each including a respective virtual BDAT driver.
8. The method of claim 6 , wherein the BIOS is a Unified Extensible Firmware Interface (UEFI) BIOS.
9. The method of claim 6 , wherein the BDAT driver is configured to communicate with the physical information handling resource via Windows Management Instrumentation (WMI).
10. The method of claim 6 , wherein the BDAT driver is a vendor-specific BDAT driver.
11. An article of manufacture comprising a non-transitory, computer-readable medium having computer-executable code thereon that is executable by a processor of an information handling system that includes a Basic Input/Output System (BIOS) and a physical information handling resource, the code configured to cause the processor to carry out steps for:
executing an operating system (OS) that includes a BIOS Data Advanced Configuration and Power Interface (ACPI) Table (BDAT) driver;
executing at least one virtual machine (VM) that includes a virtual BDAT driver;
detecting an event notification generated by the physical information handling resource; and
transmitting, to the VM, information regarding the event notification via the BDAT driver and the virtual BDAT driver, wherein the transmitting includes transmitting the information according to a vendor-specific BDAT schema via a secure reserved memory region of a memory map of the information handling system by:
the BDAT driver querying the information handling system to retrieve a key associated with the secure reserved memory region;
the BDAT driver transmitting the key to the virtual BDAT driver of the VM; and
the VM accessing the secure reserved memory region with the key.
12. The article of claim 11 , wherein the information handling system is configured to execute a plurality of VMs each including a respective virtual BDAT driver.
13. The article of claim 11 , wherein the BIOS is a Unified Extensible Firmware Interface (UEFI) BIOS.
14. The article of claim 11 , wherein the BDAT driver is configured to communicate with the physical information handling resource via Windows Management Instrumentation (WMI).
15. The article of claim 11 , wherein the BDAT driver is a vendor-specific BDAT driver.