Automotive Whitepapers: Difference between revisions
From Xen
Jump to navigationJump to search
Lars.kurth (talk | contribs) No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
* [[:File:Co-processor_management_under_xen.pdf|Managing coprocessors for Linux PV domains by running a Xen hypervisor on ARM platforms]] by Andrii Tseglytskyi ''2015-01-14, GlobalLogic'' |
* [[:File:Co-processor_management_under_xen.pdf|Managing coprocessors for Linux PV domains by running a Xen hypervisor on ARM platforms]] by Andrii Tseglytskyi ''2015-01-14, GlobalLogic'' |
||
{{Quote|As modern ARM SoCs become faster and faster, they are now capable of performing the same highload tasks that desktop PCs were performing a few years ago, such as HD video playback and highspeed graphic rendering. The structure of an ARM SoC is also now quite complicated. In addition to containing a CPU module or modules, it also includes several peripheral modules (e.g., UARTs, Wireless, HDMI ports, etc.) and coprocessors that are designed to help with highload tasks like Graphic Processor Unit (GPU) or Video Processor Unit (VPU) are assembled together with the main CPU on almost all modern ARM SoCs that are designed for mobile and automotive markets. The article will cover few aspects of sharing such coprocessors when running Xen on embedded SoC.}} |
{{Quote|As modern ARM SoCs become faster and faster, they are now capable of performing the same highload tasks that desktop PCs were performing a few years ago, such as HD video playback and highspeed graphic rendering. The structure of an ARM SoC is also now quite complicated. In addition to containing a CPU module or modules, it also includes several peripheral modules (e.g., UARTs, Wireless, HDMI ports, etc.) and coprocessors that are designed to help with highload tasks like Graphic Processor Unit (GPU) or Video Processor Unit (VPU) are assembled together with the main CPU on almost all modern ARM SoCs that are designed for mobile and automotive markets. The article will cover few aspects of sharing such coprocessors when running Xen on embedded SoC.}} |
||
* [[:File:Device_passthrough_xen.pdf|Device Passthrough to Driver Domain in Xen]] by Yurii Konovalenko ''2015-02-25, GlobalLogic'' |
|||
{{Quote|As we all know, one of the most common sources of OS crashes are hardware drivers and the issues with them. On systems with visualization, it seems logical to create a separate domain and place hardware drivers (or at least the buggiest of them) there. One of the most significant tasks of creating a system with such a driver domain is to correctly provide it with resources (e.g., IO memory, IRQs). The main idea of passthrough described in the paper is to grant access for DomD through Dom0.}} |
|||
[[Category:Embedded and Automotive PV Drivers]] |
[[Category:Embedded and Automotive PV Drivers]] |
||
Revision as of 10:18, 25 February 2015
- Managing coprocessors for Linux PV domains by running a Xen hypervisor on ARM platforms by Andrii Tseglytskyi 2015-01-14, GlobalLogic
As modern ARM SoCs become faster and faster, they are now capable of performing the same highload tasks that desktop PCs were performing a few years ago, such as HD video playback and highspeed graphic rendering. The structure of an ARM SoC is also now quite complicated. In addition to containing a CPU module or modules, it also includes several peripheral modules (e.g., UARTs, Wireless, HDMI ports, etc.) and coprocessors that are designed to help with highload tasks like Graphic Processor Unit (GPU) or Video Processor Unit (VPU) are assembled together with the main CPU on almost all modern ARM SoCs that are designed for mobile and automotive markets. The article will cover few aspects of sharing such coprocessors when running Xen on embedded SoC.
- Device Passthrough to Driver Domain in Xen by Yurii Konovalenko 2015-02-25, GlobalLogic
As we all know, one of the most common sources of OS crashes are hardware drivers and the issues with them. On systems with visualization, it seems logical to create a separate domain and place hardware drivers (or at least the buggiest of them) there. One of the most significant tasks of creating a system with such a driver domain is to correctly provide it with resources (e.g., IO memory, IRQs). The main idea of passthrough described in the paper is to grant access for DomD through Dom0.
