A computing device for native code invocation, the computing device comprising: an operating system to (i) execute a firmware method with a virtual machine in an operating system context, (ii) invoke a callback to a bridge driver in the operating system context in response to execution of the firmware method, and (iii) invoke, by the bridge driver, a firmware runtime service in the operating system context in response to invocation of the callback; wherein the computing device is configured to bind the bridge driver to the virtual machine; wherein the computing device is configured to invoke an ACPI source language context; wherein the bridge driver is configured to invoke the firmware runtime service in a de-privileged container that prevents access to sensitive hardware resources and/or other data of the computing device; and a firmware environment to execute a native code handler in the operating system context in response to invocation of the firmware runtime service, wherein: to execute the native code handler comprises to execute the native code handler in the de-privileged container, the operating system is further to configure, by the bridge driver, a memory page table for the de-privileged container in response to the invocation of the callback, and to execute the native code handler in the de-privileged container comprises to execute the native code handler in a virtual addressing mode with access restrictions imposed by the memory page table to prevent access by the native code handler to sensitive hardware resources and/or other data of the computing device. an operating system to (i) execute a firmware method with a virtual machine in an operating system context, (ii) invoke a callback to a bridge driver in the operating system context in response to execution of the firmware method, and (iii) invoke, by the bridge driver, a firmware runtime service in the operating system context in response to invocation of the callback; wherein the computing device is configured to bind the bridge driver to the virtual machine; wherein the computing device is configured to invoke an ACPI source language context; wherein the bridge driver is configured to invoke the firmware runtime service in a de-privileged container that prevents access to sensitive hardware resources and/or other data of the computing device; and a firmware environment to execute a native code handler in the operating system context in response to invocation of the firmware runtime service, wherein: to execute the native code handler comprises to execute the native code handler in the de-privileged container, the operating system is further to configure, by the bridge driver, a memory page table for the de-privileged container in response to the invocation of the callback, and to execute the native code handler in the de-privileged container comprises to execute the native code handler in a virtual addressing mode with access restrictions imposed by the memory page table to prevent access by the native code handler to sensitive hardware resources and/or other data of the computing device. to execute the native code handler comprises to execute the native code handler in the de-privileged container, the operating system is further to configure, by the bridge driver, a memory page table for the de-privileged container in response to the invocation of the callback, and to execute the native code handler in the de-privileged container comprises to execute the native code handler in a virtual addressing mode with access restrictions imposed by the memory page table to prevent access by the native code handler to sensitive hardware resources and/or other data of the computing device.