Secure virtualization for third party graphics drivers

6:

• The method of claim 1, wherein performing the memory validation comprises:
• executing a first memory validation process and a second memory validation process;
• allocating, by the first memory validation process, each type of the memory available for allocation according to the graphical rendering application programming interface;
• configuring each type of the memory available for allocation for mapping between the first memory validation process and the second memory validation process;
• writing, by the second memory validation process, a known graphical element or buffer to each type of the memory;
• determining, by the first memory validation process, that the known graphical element or buffer is accessible by the first memory validation process for one or more of each type of the memory;
• and
• outputting the one or more types of the memory for which the graphical element or buffer is accessible to the first memory validation process as the memory mapping information.

7:

• The method of claim 6,
• wherein each type of the memory conforms to the graphical rendering application programming interface,
• wherein at least one of type of the memory that conforms to the graphical rendering application programming interface is required to be successfully mapped in order to execute the graphics rendering process separately from the main process, and
• wherein the at least one type of memory required to be successfully mapped in order to execute the graphics rendering process is a host visible type in which the guest operating system is able to access the type of memory for purposes of rendering the graphics by the application via the main process.

11:

• A computing device comprising:
• a memory configured to store a host operating system;
• and
• processing circuitry configured to:
• execute the host operating system, which is configured to initiate execution of a main process that emulates a guest operating system to support execution of an application native to the guest operating system,
• wherein the main process is configured to:
• initiate execution of a graphics rendering process separate from the main process, the graphics rendering process configured to handle graphics rendering on behalf of the main process;
• responsive to initiating execution of the graphics rendering process, perform a memory validation to obtain memory mapping information that identifies memory within the computing device that is available for mapping between the main process and the graphics rendering process;
• and
• configure the main process to support the mapping of the memory between the main process and the graphics rendering process to facilitate execution of a graphical rendering application programming interface used by the application for rendering graphics.

16:

• The computing device of claim 11,
• wherein the main process is, when configured to perform the memory validation, is configured to execute a first memory validation process and a second memory validation process,
• wherein the first memory validation process is configured to:
• allocate each type of the memory available for allocation according to the graphical rendering application programming interface;
• and
• configure each type of the memory available for allocation for mapping between the first memory validation process and the second memory validation process;
• wherein the second memory validation process is configured to write a known graphical element or buffer to each type of the memory, and
• wherein the first memory validation process is further configured to:
• determine that the known graphical element or buffer is accessible by the first memory validation process for one or more of each type of the memory;
• and
• output the one or more types of the memory for which the graphical element or buffer is accessible to the first memory validation process as the memory mapping information.

17:

• The computing device of claim 16,
• wherein each type of the memory conforms to the graphical rendering application programming interface,
• wherein at least one of type of the memory that conforms to the graphical rendering application programming interface is required to be successfully mapped in order to execute the graphics rendering process separately from the main process, and
• wherein the at least one type of memory required to be successfully mapped in order to execute the graphics rendering process is a host visible type in which the guest operating system is able to access the type of memory for purposes of rendering the graphics by the application via the main process.

20:

• A non-transitory computer-readable storage medium having instructions stored thereon that, when executed, cause one or more processors to:
• execute a host operating system, which is configured to initiate execution of a main process that emulates a guest operating system to support execution of an application native to the guest operating system,
• wherein the main process is configured to:
• initiate execution of a graphics rendering process separate from the main process, the graphics rendering process configured to handle graphics rendering on behalf of the main process;
• responsive to initiating execution of the graphics rendering process, perform a memory validation to obtain memory mapping information that identifies memory within the computing device that is available for mapping between the main process and the graphics rendering process;
• and
• configure the main process to support the mapping of the memory between the main process and the graphics rendering process to facilitate execution of a graphical rendering application programming interface used by the application for rendering graphics.