Computer System Executing Multiple Operating Systems

2. The computing device of claim 1, wherein the first operating system and the second operating system are existing operating systems, the common kernel driver being generated by merging a functionality of a first kernel driver with a functionality of a second kernel driver, wherein the first kernel driver and the second kernel driver are existing kernel drivers that are otherwise known to be used in the first operating system and the second operating system, respectively.

3. The computing device of claim 2, wherein the common kernel driver is generated by modifying the first kernel driver to include the functionality of the second kernel driver.

4. The computing device of claim 2, wherein the functionality of the first kernel driver is merged with the functionality of the second kernel driver at a level of calling conventions known to be used in function calls made in the first kernel driver and the second kernel driver.

5. The computing device of claim 1, wherein the computer-executable instructions, when executed, cause the processor to employ a handler of the common kernel driver to determine which one of the first user space driver and the second user space driver made the given function call to the common kernel driver, based on differences in attributes of a first parameter and attributes of a second parameter, when the first user space driver and the second user space driver access the common kernel driver via a same path, wherein the first parameter and the second parameter are passed by the first user space driver and the second user space driver, respectively, to the common kernel driver.

6. The computing device of claim 5, wherein the attributes of the first parameter and the attributes of the second parameter comprise at least one of: a data size, a data type, a data order.

7. The computing device of claim 1, wherein the computer-executable instructions, when executed, cause the processor to employ a handler of the common kernel driver to determine which one of the first user space driver and the second user space driver made the given function call to the common kernel driver, based on at least one symbolic link or a bind mount provided in a given path, when the first user space driver and the second user space driver access the common kernel driver via a first path and a second path, respectively.

8. The computing device of claim 1, wherein the computer-executable instructions, when executed, cause the processor to employ a handler of the common kernel driver to determine which one of the first user space driver and the second user space driver made the given function call to the common kernel driver, based on a difference between a first driver configuration and a second driver configuration employed by the first user space driver and the second user space driver, respectively.

10. The method of claim 9, wherein the first operating system and the second operating system are existing operating systems, the common kernel driver being generated by merging a functionality of a first kernel driver with a functionality of a second kernel driver, wherein the first kernel driver and the second kernel driver are existing kernel drivers that are otherwise known to be used in the first operating system and the second operating system, respectively.

11. The method of claim 10, wherein the common kernel driver is generated by modifying the first kernel driver to include the functionality of the second kernel driver.

12. The method of claim 10, wherein the functionality of the first kernel driver is merged with the functionality of the second kernel driver at a level of calling conventions known to be used in function calls made in the first kernel driver and the second kernel driver.

13. The method of claim 9, further comprising employing a handler of the common kernel driver to determine which one of the first user space driver and the second user space driver made the given function call to the common kernel driver, based on differences in attributes of a first parameter and attributes of a second parameter, when the first user space driver and the second user space driver access the common kernel driver via a same path, wherein the first parameter and the second parameter are passed by the first user space driver and the second user space driver, respectively, to the common kernel driver.

14. The method of claim 13, wherein the attributes of the first parameter and the attributes of the second parameter comprise at least one of: a data size, a data type, a data order.

15. The method of any of claim 9, further comprising employing a handler of the common kernel driver to determine which one of the first user space driver and the second user space driver made the given function call to the common kernel driver, based on at least one symbolic link or a bind mount provided in a given path, when the first user space driver and the second user space driver access the common kernel driver via a first path and a second path, respectively.

16. The method of claim 9, further comprising employing a handler of the common kernel driver to determine which one of the first user space driver and the second user space driver made the given function call to the common kernel driver, based on a difference between a first driver configuration and a second driver configuration employed by the first user space driver and the second user space driver, respectively.