ACRN Project Technical Community Meeting Minutes - 9/5/2018
Meeting Minutes Archive: https://drive.google.com/drive/u/2/folders/1_XTGu6re3BOQAjtPx636Mz1T5lOy2UWC
ACRN Project TCM - 5th September 2018
Attendees (Total 43, 9/5)
Download foil from ACRN Presentation->ACRN_TCM->WW36’18.
Q: How many maximum vCPU can be supported on Apollo Lake platform? A: 4 vCPU.
Q: Is there any communication b.w. these vcpu threads? A: Yes, the IPI is used to communicate between the vcpu threads.
We don't support the CPU sharing so far, the main reason of introducing the scheduler is to manage the lifecycle of the guests. Imagine that we need to destroy the vcpus when its serving VM is shutdown, and we need to put its physical CPUs to some state even if the vcpu is destroyed. that state is default idle. In order to switch the default idle and vcpu thread, we introduced the scheduler to make it simple. That means the current scheduler is only able to schedule between vcpu thread and default idle thread on the same physical CPU.
Q: What is the real mode address for AP? how was it handle before vSBL introduction? A: AP reset vector is provided by SIPI message which is sent by BSP, no matter vSBL is used or not. that means AP real mode address is decided by the OS when it boots smp secondary CPUs, not by hypervisor.
Q: OS uses AFAIK a real mode address from ACPI region I think 0x90000-0xA00000. how this mem is accessable to guest if ACPI is not passthru to guest?
Q: How extensive is your instruction decoder wrt the full Intel instruction set? Are you focusing on specific read and write instructions or does Intel have a full instruction set decoder?
Tel: +86-21-6116 7445
MP: +86-1364 1793 689