I tried to debug the virtualization code on the Neoverse N2 FVP platform, but found that the performance of the fvp was particularly poor and affected the interaction. How can I debug virtualization code efficiently？

1. The DDR memory on my server is 397GB, not hard disk memory.

2. I run the rsync command to copy the linux kernel to host(fvp) from the machine where RDN2 FVP is deployed without going through an external network.

3. I tested again. During the startup of host kernel and after the completion of the startup of host kernel, only a certain core always has a 100% utilization rate at the same time, while the utilization rate of other cores is very low.

4. There are two hyperlinks below. Following the operation of the first hyperlink, the performance of fvp can work normally, while following the operation of the second hyperlink, the performance of fvp cannot work normally, which is also the reason why I put forward this question. What is the immediate difference between the two? My guess is that buildroot boot generates more workload than busybox boot

1. The DDR memory on my server is 397GB, not hard disk memory.

2. I run the rsync command to copy the linux kernel to host(fvp) from the machine where RDN2 FVP is deployed without going through an external network.

3. I tested again. During the startup of host kernel and after the completion of the startup of host kernel, only a certain core always has a 100% utilization rate at the same time, while the utilization rate of other cores is very low.

4. There are two hyperlinks below. Following the operation of the first hyperlink, the performance of fvp can work normally, while following the operation of the second hyperlink, the performance of fvp cannot work normally, which is also the reason why I put forward this question. What is the immediate difference between the two? My guess is that buildroot boot generates more workload than busybox boot