I followed the steps in the hyperlink below to start host and guest
docs/infra/common/gicv4_1-vlpi-vsgi.rst · master · Arm Reference Solutions / arm-reference-solutions-docs · GitLab
There are a few problems here：
Firstly,it takes an hour and a half to start host, then a long time to start guest.
Secondly,copying the kernel source code to host ，need several hours.
Thirdly,in order to make vmlinux and kernel source consistent, I need to update the kernel of host, but I cannot compile and install the kernel, the performance of fvp is too poor.
How can I debug virtualization code efficiently？
Hi Stephen
Thank you for your help. The above is my reply. You can focus on the difference between the two hyperlinks.
Best Regards,Mikhail
Hi MikhailWe've investigated further and have some more information for you.Fast Models are currently single-threaded for the main simulation. There are a few utility threads, but most of the simulation happens in a single thread, which is why you are seeing high utilization on a single host core.On your second point (copying the kernel source code to host), you should be able to mount the model's filesystem directly from the host, and then directly load e.g. an ext4 image. There's no need to involve the model in any copying process.You asked about the difference between the two GitLab links.For the first one, Busybox boot is comparatively light weight boot as the filesystem is RAM based.For the second one, GIC testing, a distribution-based boot is used which involves multiple things such as PCIe I/O, Disk I/O, and usage of kernel storage stack. Booting of distros is quite slow on models because of these reasons. Using a Debian distribution that is lighter in comparison to Ubuntu may help to some extent.Hope this helpsStephen