You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 55 Next »


2020

Jul 22, 2020

Attendees:

  • Jerry Zhao - Panasonic
  • Walt Miner - Linux Foundation
  • Scott Murray - Konsulko
  • Tadao Tanikawa - Panasonic
  • Takashi Tsubone - Panasonic
  • Mikhail Golubev - Open Synergy
  • Alex Bennée - Linaro
  • Francois Ozog - Linaro
  • Victor Duan - Linaro
  • Vincent Guittot - Linaro
  • Kenji Hosokawa - ADIT
  • Yuki Tsunashima - ADIT
  • Jakub Luzny - GSoC student
  • Parth Dode - GSoC student

Agenda: 


Aug 5, 2020

Attendees:

  • Jerry Zhao - Panasonic
  • Walt Miner - Linux Foundation
  • Scott Murray - Konsulko
  • Tadao Tanikawa - Panasonic
  • Takashi Tsubone - Panasonic
  • Mikhail Golubev - Open Synergy
  • Laurent Cremmer -Carmeq
  • Mark Silberberger - Carmeq
  • Nicolas Blazevic - Carmeq 
  • Alex Bennée - Linaro
  • Mike Holmes - Linaro
  • Victor Duan - Linaro
  • Kenji Hosokawa - ADIT
  • Jakub Luzny - GSoC student
  • Rich Persaud

Agenda: 

  • Topic 1: Yocto Architecture for VirtIO FEDD integration Mikhail Golubev
    • some SoC vendor's BSP kernel doesn't support Yocto Linux so that the virtio.scc may be not included.
    • it's better to maintain the front end driver or the kernel configuration in AGL.
    • Release candidate branch for AGL will be in January.
    • general idea is on master, but for recipe (patch and yocto layer only) → sandbox, source code → code repository
      Jerry, Jiancong Zhao need to check with Walt Miner on application of a new repository (JIRA ticket)
  • Topic 2: VirtIO Backend Related Sharing  Laurent Cremmer
  • Topic 3: GSoC Project Progress Sharing Month #2 Parth Dode Jakub Luzny → move to next EG

Aug 19, 2020

Attendees:

  • Jerry Zhao - Panasonic
  • Walt Miner - Linux Foundation
  • Scott Murray - Konsulko
  • Tadao Tanikawa - Panasonic
  • Mikhail Golubev - Open Synergy
  • Laurent Cremmer -Carmeq
  • Mark Silberberger - Carmeq
  • Francois Ozog - Linaro
  • Victor Duan - Linaro
  • Kenji Hosokawa - ADIT
  • Yuki Tsunashima - ADIT
  • Eva Rio - Tuxera
  • Joel Catala - Tuxera
  • Christoph Mutz - Western Digital
  • Matteo Zammattio - Western Digital
  • Jakub Luzny - GSoC student
  • Parth Dode - GSoC student
  • Rich Persaud

Agenda: 

  • Topic 1: GSoC Project Progress Sharing Month #2 Parth Dode Jakub Luzny 
  • Topic 2: Follow-up Proposal for VirtIO Front-end Integration Mikhail Golubev
  • Topic 3: Guest Speech on Xen Argo with VirtIO by Edgeform Chritopher Clark & Rich Persaud

Remaining Action Items:


Sep 2, 2020

Attendees:

  • Jerry Zhao - Panasonic
  • Walt Miner - Linux Foundation
  • Jan-Simon Moeller - Linux Foundation
  • Scott Murray - Konsulko
  • Mikhail Golubev - Open Synergy
  • Laurent Cremmer -Carmeq
  • Mark Silberberger - Carmeq
  • Francois Ozog - Linaro
  • Victor Duan - Linaro
  • Kenji Hosokawa - ADIT
  • Yuki Tsunashima - ADIT
  • Eva Rio - Tuxera
  • Joel Catala - Tuxera
  • Christoph Mutz - Western Digital
  • Marius Vlad - Collabora
  • Jakub Luzny - GSoC student
  • Parth Dode - GSoC student
  • Rich Persaud

Agenda: 

  • Topic 1: Final Presentation of GSOC Jailhouse Project Jakub Luzny Parth Dode
  • Topic 2: Follow-up Q&A about virtio-argo (Chritopher Clark & Rich Persaud)
  • Topic 3: Conclusion & Future Plan of AGL KK VirtIO Integration Mikhail Golubev
    Mikhail Golubev  please upload the slide you presented in last EG

Sep 16, 2020

Attendees:

  • Jerry Zhao - Panasonic
  • Walt Miner - Linux Foundation
  • Jan-Simon Moeller - Linux Foundation
  • Scott Murray - Konsulko
  • Mikhail Golubev - Open Synergy
  • Laurent Cremmer -Carmeq
  • Mike Holmes - Linaro
  • Francois Ozog - Linaro
  • Victor Duan - Linaro
  • Kenji Hosokawa - ADIT
  • Yuki Tsunashima - ADIT
  • Tadao Tanikawa - Panasonic
  • Eva Rio - Tuxera
  • Joel Catala - Tuxera
  • Christoph Mutz - Western Digital
  • Marius Vlad - Collabora

Agenda: 

  • Topic 1: Future Plan of VirtIO Device in AGL
    • virtio-can not virtio-vehicle (virtio-can also include LIN)
    • virtio-camera: what is up with DRM?
    • virtio-tuner not virtio-radio (Linux v4l2 interface)
    • ACRN has smth for USB → needs to be checked
    • GNSS via virito-scmi? → needs to be checked
    • Mikhail Golubev  to upload the slide.

Sep 30, 2020

Attendees:

  • Jerry Zhao - Panasonic
  • Walt Miner - Linux Foundation
  • Jan-Simon Moeller - Linux Foundation
  • Scott Murray - Konsulko
  • Mikhail Golubev - Open Synergy
  • Nicolas Blazevic - Carmeq
  • Victor Duan - Linaro
  • Francois Ozog - Linaro
  • Tadao Tanikawa - Panasonic
  • Christoph Mutz - Western Digital
  • Matteo Zammattio - Western Digital
  • Marius Vlad - Collabora

Agenda: 

  • Topic 1: Future Plan of VirtIO Device in AGL
    • How we can brainstorm what kind of virtio devices are necessary to AGL
      • method 1: invite IVI, IC experts from other EG to join the discussion
        • Email in the mailing list is okay
        • Inter-EG activities are handled in the SAT
        • Announce & Invite in Dev Call is also possible (most people)
      • method 2: invite GENIVI AVPS member to share their progress on the automotive virtio discussion
    • What is our policy to decide which device should be integrated into AGL
      • Option 1 (most strict): Only if the device has been upstreamed and official published in the OASIS specification
        • Publish of OASIS specification will be the trigger for AGL virtio porting activities
      • Option 2 (moderate): If the device has been upstreamed and has a certain plan to be included in the OASIS specification in near future
      • Option 3 (most loose): Any devices that Virtualization EG members have consensus

        Discussion:
      • Upstreamed drivers are mandatory
      • Depending on AGL kernel version, some new devices may not be included. Backporting from the newer kernel is needed (in some circumstances, trouble may happen) → discuss whether it can be integrated in the form inside kernel trees or out of the kernel trees
      • New device drivers (not upstreamed) has the similar situation with the above

        Conclusion:
        Depending on the maturity of the virtio device drivers, we can put into different places → all virtio drivers can be integrated in this way
      • Recipe: Put the new drivers to the meta-agl-devel for developing and testing, integrate the stable drivers in the meta-agl.
      • Source Code: Staging (new drivers) & Src (stable drivers)
  • Topic 2: OpenSynergy Plans for ALS VirtIO PoC & AGL KK Contribution Mikhail Golubev
    OpenSynergy will distribute the PoC after KK contribution as a reference implementation of VirtIO. Jan Simon has suggested distributing methods such as "accepting terms" which already used by some AGL mebmer. 

Oct 14, 2020

Attendees:

  • Jerry Zhao - Panasonic
  • Walt Miner - Linux Foundation
  • Jan-Simon Moeller - Linux Foundation
  • Scott Murray - Konsulko
  • Mikhail Golubev - Open Synergy
  • Laurent Cremmer -Carmeq
  • Mark Silberberger - Carmeq
  • Nicolas Blazevic - Carmeq
  • Mike Holmes - Linaro
  • Alex Bennée - Linaro
  • Victor Duan - Linaro
  • Misami Hiramatsu - Linaro
  • Kenji Hosokawa - ADIT
  • Tadao Tanikawa - Panasonic

Agenda: 

  • Topic 1: Linaro Sharing for ALS PoC VICTOR DUAN
    • AGL is working as a guest (front end)
    • Hypervisor: KVM & Xen
    • Hardware: different ARM boards (Socionext Developer Box, Armas 8040 MacchiatoBin)
    • portability across different platform (independent from SoC & Hypervisor)
    • virtio devices: virtio-net, virtio-blk, virtio-gpu. future: virtio-video, virtio-rpmb and etc.
    • no special preference on whether virtio-pci or virtio-mmio
    • the memory access limit will be not in the scope of the demo
    • Xen hypervisor: similar approach to crosvm
    • Original Target: End of this month (but it is postponed)
    • for the ALS: blk, network and framebuffer (audio will be difficult for the current schedule)
    • Work will be open.
    • Progress can be traced in the following path: https://collaborate.linaro.org/pages/viewpage.action?pageId=147423498

  • Topic 2: ALS Presentation

    https://ossalsjp20.sched.com/

    Video Submit Deadline: ? Walt Miner

Walt Miner to update the attendee of today's meeting

fix the link issue on the Wiki


Nov 11, 2020

Attendees:

  • Jerry Zhao - Panasonic
  • Walt Miner - Linux Foundation
  • Jan-Simon Moeller - Linux Foundation
  • Scott Murray - Konsulko
  • Mikhail Golubev - Open Synergy
  • Mark Silberberger - Carmeq
  • Alex Bennée - Linaro
  • Victor Duan - Linaro
  • Tadao Tanikawa - Panasonic
  • Christoph Mutz - Western Digital
  • Joel Catala - Tuxera

Agenda: 

  • Topic 1: Virtualization Webinar
    Webinar: Device Virtualization Architecture, Panasonic

    When:
    Thursday, 12 November 2020
    10:00pm to 11:00pm
    (UTC+00:00) UTC

    Where:
    Registration Required - See link below

    Organizer: Emily Olin eolin@linuxfoundation.org

    Description:

    AGL Community:

    We are very excited to kick-off a new webinar series that will feature presentations from AGL members on open source technologies, trends, product/project updates, tutorials, and more. 

    Please register to join us for our first webinar on November 12th at 2:00 pm PT:

    Device Virtualization Architecture in Automotive

    Mizuyama Masashige, Automotive CTO, Panasonic

    Thursday, November 12 at 2:00 PM Pacific 

    (Friday, November 13 at 7:00 am Japan)

    Registration link

  • Topic 2: ALS Presentation & AGL KK VirtIO Porting Progress Checking
    - Linaro: Jellyfish
     a) KVM works fine. → working fine on the real board
     b) Xen Dom0 works fine.  has some trouble with DomU (on QEMU is okay, but on hardware still some ongoing issues)?
       Xen virtio implementation → only supported virtio blk device

    - OpenSynergy:

    Mikhail Golubev  please upload the slides you presented here.
    on-schedule for the KK virtio porting



  • Suggestion: Upload the demo video of EG PoC after ALS demo onto the AGL official Youtube channel
    Pending Mikhail Golubev VICTOR DUAN to check internally if this is okay 
    (https://www.youtube.com/channel/UC1axavgir413w00rwBHPAtQ)

Nov 25, 2020

Attendees:

Agenda: 

  • Topic 1: VirtIO KK Porting Progress Mikhail Golubev
    • AGL KK progress is fine.
    • only virtio-input multi-touch patch is still not available because not upstreamed in the Linux kernel main line (waiting for the LKML to accept)
    • Yocto machine: merged in the AGL and additionally 
    • Question: demo image (set-up)
      → hypervisor distribution: Mikhail Golubevcheck internally
      → QEMU can also be also considered.
      VICTOR DUAN tell us where we can find the implementation of Linaro's ALS QEMU demo  
    • Question: Passthrough for GPU-3d?
      • yes, for ALS
      • for KK porting and reference implementation. VirtIO-gpu3d will be used insead
  • Topic 2: ALS Presentation from Demo Jerry, Jiancong Zhao

Dec 9, 2020

Attendees:

Agenda: 

  • Virtual F2F Session in SAT

    • ALS 2020 video:
      • Linaro: 
      • OpenSynergy:
         

2021

Jan 13, 2021

Attendees:

  • Jerry Zhao - Panasonic
  • Jan-Simon Moeller - Linux Foundation
  • Scott Murray - Konsulko
  • Mikhail Golubev - Open Synergy
  • Laurent Cremmer - Carmeq
  • Victor Duan - Linaro
  • Tadao Tanikawa - Panasonic
  • Binghua - Qualcomm
  • Sonic - ?

Agenda: 

  • Quick summary of virtual SAT on  
  • Progress of virtio reference implementation Mikhail Golubev
    • The PoC will be ready by April and able to request download from AGL websites
    • The backend and HV are proprietary but frontend (including virtio drivers) are open and can be customized

      → Announce the new virtio feature and reference implementation on KK in AB and AMM(?) Walt Miner
      → After moving to meta-agl, it can be announced
       A draft of two/three scentences are needed

Build Instruction → e.g. https://docs.automotivelinux.org/en/master/#0_Getting_Started/2_Building_AGL_Image/5_2_Raspberry_Pi_4/

Jan-Simon Moeller create new category for virt-EG to write documentation about virtio

  • Collaboration proposal from RHSA-EG (Mazda is the leader)
    • Present the reference implementation PoC in AMM
    • What is the deadline for CFP
  • Workshop for discussion about virtio planned to be held after new year (rough plan)
    • 1st Open Discussion Workshop: Optimization of VirtIO-gpu3d (how to achieve zero-copy in gpu 3d mode)   
    • 2nd Open Discussion Workshop: What devices need to be virtualized for an virtual AGL (what else virtio-devices needed for AGL)  TBD
  • Future EG Planning
    •  1st Workshop (virtio-gpu3d topic) → Jerry, Jiancong Zhao  will email to invite community members (especially gpu, mesa/virgl expert to join)
    •  normal EG session
    • TBD: 2nd Workshop (necessary virtual devices for AGL) → Jerry, Jiancong Zhao  will email to invite community members (especially gpu and virtio expert to join)

      Walt Miner please share the google doc link of past EG white paper.
  • Last but important:
    • Thanks so much for all the EG members for great work in  2020! Happy new year!

Jan 20, 2021

Attendees:

  • Jerry Zhao - Panasonic
  • Jan-Simon Moeller - Linux Foundation
  • Scott Murray - Konsulko
  • Mikhail Golubev - Open Synergy
  • Vasyl Vavrychuk - OpenSynergy
  • Andriy Tryshnivsky - OpenSynergy
  • Laurent Cremmer - Carmeq
  • Mark Silberberg - Volkswagen
  • Victor Duan - Linaro
  • Alex Bennée (Stratos Tech Lead) - Linaro
  • Peter Griffin (Multimedia Tech Lead) - Linaro 
  • Tadao Tanikawa - Panasonic
  • Binghua - Qualcomm
  • Marius Vlad - Collabora
  • Tadao Tanikawa - Panasonic
  • Kenji Hosokawa - ADIT

  • Harunobu Kurokawa - Renesas

  • Masahiro Hasegawa - Renesas

  • Tomeu Vizoso

  • Venkata Ramalinga Prasad Tadepalli

  • Parag Borkar - OpenSynergy

Agenda: 

  • 1st VirtIO Workshop: VirtIO GPU-3d Performance - How to achieve Zero-Copy with AGL
  • Open Synergy Slides (How to achieve zero-copy on Renesas SoC)
    VirtIO_GPU_3D_Workshop.pdf
    • cache coherence between CPU/GPU
    • Discussion Points:
      • Does VirtIO GPU supports zero-copy in QEMU, crosvm, etc?
        • crosvm uses host allocations, is it requirement for something?
        • progress in crosvm is on-going and realted to Vulkan.
        • crosvm use the virtio-pci (to expose host memory to guest - which also avoid memory copy)
        • Any available standard solution/platform to solve this zero-copy for the AGL community
          • Tomeu: Collabora is having project in ChromeBook (which is more focusing on gaming) but expose host memory to guest
          • Alex: not using virtio-pci may be the limitation (kiran explained why it is not because limitation →with 64 bit PCI addressing the windows are more than large enough)
          • Conclusion: there's no good solution available at the moment for zero-copy mechanism for automotive use case
        • Note: sometimes, copying smaller buffers ( < 4k) is faster then using zero copying
      • Does virglrender supports zero-copy of OpenGL buffers (vertex buffer, element buffer, etc.)?
        • there are some mechanisms in virglrender. no copy happened. (although some limitation may exist)
      • EXT_image_dma_buf_import fails with EGL_BAD_ACCESS
        • Tomeu: Reason is that specific platform stride requirements are not propagated to the guest. New IOCTL exist to propagate stride info to the guest, but not mainlined yet.
        • GPU/display supports only 32-bit addresses. Issue: ensure device guest (mesa) allocates memory form lower addresses
          • Bounce buffers:
            • Stratos prj is interested in a mechanism to limit guest's allocations to a particular mem window (potentially, breaking virtio driver mem model)
            • Kernel dma pools are being looked at. This will result in memcpy from userspace to kernel dma capable pool (page cache as well?)
      • Virglrenderer tests fails on R-CAR


Feb 3, 2021

Attendees:

  • Jerry Zhao - Panasonic
  • Jan-Simon Moeller - Linux Foundation
  • Scott Murray - Konsulko
  • Mikhail Golubev - Open Synergy
  • Vasyl Vavrychuk - OpenSynergy
  • Andriy Tryshnivsky - OpenSynergy
  • Laurent Cremmer - Carmeq
  • Mark Silberberg - Volkswagen
  • Victor Duan - Linaro
  • Francis Ozog - Linaro
  • Masami Hiramatsu - Linaro
  • Alex Bennée (Stratos Tech Lead) - Linaro
  • Peter Griffin (Multimedia Tech Lead) - Linaro 
  • Tadao Tanikawa - Panasonic
  • Binghua - Qualcomm
  • Marius Vlad - Collabora
  • Tadao Tanikawa - Panasonic
  • Kenji Hosokawa - ADIT

Agenda: 


Feb 17, 2021

Attendees:

  • Jerry Zhao - Panasonic
  • Jan-Simon Moeller - Linux Foundation
  • Scott Murray - Konsulko
  • Mikhail Golubev - Open Synergy
  • Vasyl Vavrychuk - OpenSynergy
  • Parag Borkar - OpenSynergy
  • Andriy Tryshnivsky - OpenSynergy
  • Laurent Cremmer - Carmeq
  • Mark Silberberg - Volkswagen
  • Victor Duan - Linaro
  • Francis Ozog - Linaro
  • Masami Hiramatsu - Linaro
  • Alex Bennée (Stratos Tech Lead) - Linaro
  • Peter Griffin (Multimedia Tech Lead) - Linaro 
  • Tadao Tanikawa - Panasonic
  • Binghua - Qualcomm
  • Marius Vlad - Collabora
  • Tadao Tanikawa - Panasonic
  • Kenji Hosokawa - ADIT

Agenda: 2nd workshop to Discuss how to achieve zero-copy for VirtIO GPU (3d mode)


Workshop Topic:
Follow up discussion on how to achieve Zero-Copy for VirtIO-GPU (3d mode)


Workshop Agenda:

  • Quick review of 1st workshop discussion*
      *For the 1st workshop meeting notes, please find at https://confluence.automotivelinux.org/display/VE/Meeting+Agenda#MeetingAgenda-Jan20,2021
  • Discussion on two methods to achieve zero-copy: dynamic vs dedicated heap
    • GPU/CPU cache coherency challenges 
    • Host allocation (share hostmem with guest) vs Guest allocation 
      • ChromeOS uses dynamic hostside allocation 
      • does host allocation and sharing introduce security concerns?
    • (over to Parag, OpenSynergy)
    • Dynamic vs Dedicated hostside allocation
      • where in host memory needs to be exposed to guest
      • host also has knowledge of where the real HW can see
    • Dedicated GPU heap (VRAM):
      • Idea: have a dedicated inter-vm shared mem area, guest requests buf params from hosts and allocates objects in shared memory and "sends" objects to host (paddrs)
      • What is needed to be done:
        • virtio gpu kernel driver adaptations → allocations from vram will be needed as well
        • MESA3d adaptations?
        • virgl adaptations
    • Can VFIO on Intel be applicable to the zero-copy case?
    • Type 1/2 HV: does the problem also apply to T2 HV?
      • There should be no difference between T1/2 HV, the same problem exists.
    • Xen HV:
      • QEmu - generic virtio backend for Xen
      • Virtio patches are being discussed
    • Updates from GPU workshop #1
      • Stride requirements were found (for RCar), hardcoded, but visual artifacts can be seen → activity postponed
  • Discuss on how we should move forward
  • Slides:


March 3, 2021

Attendees:

  • Jerry Zhao - Panasonic
  • Jan-Simon Moeller - Linux Foundation
  • Scott Murray - Konsulko
  • Mikhail Golubev - Open Synergy
  • Vasyl Vavrychuk - OpenSynergy
  • Andriy Tryshnivsky - OpenSynergy
  • Laurent Cremmer - Carmeq
  • Mark Silberberg - Volkswagen
  • Victor Duan - Linaro
  • Francis Ozog - Linaro
  • Masami Hiramatsu - Linaro
  • Alex Bennée (Stratos Tech Lead) - Linaro
  • Peter Griffin (Multimedia Tech Lead) - Linaro 
  • Tadao Tanikawa - Panasonic
  • Binghua - Qualcomm
  • Marius Vlad - Collabora
  • Tadao Tanikawa - Panasonic
  • Kenji Hosokawa - ADIT

Agenda: 

  • GSoC Proposal from Virt-EG
    • Link: https://wiki.linuxfoundation.org/gsoc/2021-gsoc-agl

    • If any EG member interested, please provide Project Name, Task Details, Exprience Level (Prerequisite Skill), Contact of Mentor by  

      • Experience Level: Description

      • Beginner:

        • Task #1: webcam demo app - write an app exposing the v4l webcam feed

          • your task will be to develop an QT/QML-based application to display the a webcam feed - talk to jsmoeller (at) linuxfoundation.org

      • Intermediate:

        • Task #2: demo app for the IIO service. Display sensor data from the iio-service on the display.

          • Your task will be to develop an QT/QML-based application to show data from sensors - talk to jsmoeller (at) linuxfoundation.org

      • Advanced:

        • Task #3: Platform Development - create or enhance the container image

          • Your task will be to either create or enhance a container-based setup using AGL - talk to jsmoeller (at) linuxfoundation.org

      • Advanced++:

        • Task #4 integration of ROS (Robot OS - meta-ros) - talk to jsmoeller (at) linuxfoundation.org

        • Task #5 extend the jailhouse support

  • VirtIO KK Release
  • All Member Meeting (Mar 16~17)
  • Follow-up of last workshop on VirtIO-gpu
    • Can VFIO on Intel be applicable to the zero-copy case?
      • Which address space are buffers in? Can we use IOMMU for that?
      • IOMMU is a must have to defeat against DMA attacks

      • Intel pioneered VFIO; Huawei did develop so called "warpdrive" technology

        Mail from Kenneth (Huawei)

        Hello, Jerry,

        Nice meeting you. We are happy to discuss UADK with colleagues of the same profession. We are just afraid that we cannot give what you need;).  Because it seems you are looking for VFIO rather than UADK. We tried to merge our requirement to VFIO initially. But we gave up after the first RFC. To us, the major down side of VFIO is that it is a practical device. But we don’t take it a device. We take it a heterogeneous CPU. In UADK, the process attach to the accelerator, the accelerator share whole or part of the address space of the process. So the process can deliver task to the accelerator without warrying how to copy data to the accelerator. So there is no independent device is created, no DNA operation is provided. It is just for sharing memory between CPU and the accelerator. Because of this, we solve different set of problem. E.g. we have to take care of process-cloning to duplicate/stop the interface to child process.

        But it seem you are looking for a solution to isolate some GPU resource for particular VM. This is exactly what VFIO trying to do.

        So now it is you who may want to tell me. Are you guys really want to know the detail of UADK? J

        Cheers

  • Future Activity of EG
    • Welcome proposal from members
  • No labels