Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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

...

  • 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:
    • View file
      namevirtiogpu3d_workshop-f1.pdf
      height250