Page Comparison

Members: 

...

...

• Purpose: To show the features and evaluate performance for VirtIO automotive use
• Define common specification, architecture and evaluation items for the EG PoC
  • Discussion on VirtIO Devices to be used in different automotive use cases (IVI, IC, Telematics)
    • what virtual devices should be used
    • how the virtual devices should be used (pass-through/front-end/back-end)
• Implementation
  • HW:
    • Emulator: QEMU 
    • SoC: TBD
      • Options:
        • Renesas M3/H3 (H3 is hard to get for some members)
        • Qualcomm Board
        • QEMU x86
        • other companies' SoC
    • HW: TBD
      
      • Options:
        • Renesas Reference Board
        • LEGO
        • ...
  • SW: 
    
    • Hypervisor: Any OSS/commercial hypervisor that supports VirtIO
    • Front-end Device Driver: Open Source
    • Back-end Device Driver: Proprietary for most of the case (QEMU has open source backend) 
  • How:
    • idea: break down to several PoCs with incremental features
      • step 1: common/basic feature only (only 1 guest VM, only simple virtio devices such as virtio-blk, virtio-net)
      • step 2: more advanced feature
  • Who:
    • option 1: voluntary implementation from members (PoC in the name of the company/community)
    • option 2: get funding support from Linux Foundation (PoC in the name of AGL community)
  • Potential Target Event:
    Walt Miner to check if possible to present PoCs in the name of Virtualization EG (ALS, AMM)
    • 2020.9 AGL ALS
    • 2021.1 CES2021
    • 2021.3 AGL AMM

...

• Yocto layer to enable user to choose whether to use VirtIO or not.
• Introduce virtio-blk, net, console, random generator, gpu2d&3d in AGL K
  • release date: 12 Feb 21, 2021 
  • release candidate 1: Dec 2, 2020 20 Nov 2020 
  • release candidate 2: Nov  02 Dec 2020 
    (ddl to include new feature in to AGL K is RC2)
• Introduce other standardized and upstream available virtio devices in AGL L