ACRN Project Technical Community Meeting Minutes - 4/3/2019
Meeting Minutes Archive: Google doc: https://drive.google.com/drive/u/2/folders/111m6iU3PjSZebOOKzLagYPUWMvseGLeU
ACRN Project TCM - 3rd April 2019
ACRN brochure updated with architecture picture.
Download foil from ACRN Presentation->ACRN_TCM->WW14’19
Q1: Are there any device sharing between Safety VM and other VM?
A1: No, due to safety consideration.
Q2: ACRN is designed for small footprint for IoT usage, will this design provide different compile configuration to control the device driver code in ACRN hypervisor? What’s the drawback of moving device support from SOS to HV? Portability, more platform scalability?
A2: It depends on how many new code will be added for the devices moved from SOS to HV. We prefer to use unified code base to handle the different requirements. That will minimize the maintaining/testing efforts. But if footprint is impacted, we will figure out how to handle it. Compiling configuration could be one option.
Besides the footprint, the portability could be a drawback. Because different platform has different system critical devices. Then we need move all these system critical devices from SOS to HV. More platform specific code will be added to HV and hurt HV portability.
Q3: Does the safety vm feature feature exist in the acorn master or special branch? When?
A3: It will be landed to master branch. The rough timeline could be Q3.
Q4: Will ACRN use Post interrupt to guarantee the real time?
A4: Now, we use lapic passthru for hard realtime VM. It could minimize the HV impaction to real time task in RTVM.
Tel: +86-21-6116 7445
MP: +86-1364 1793 689