Assessment of the difficulty in porting CPU architecture for xen
-
Hello everyone! I am working on implementing a tool to assess the complexity of CPU architecture porting. It primarily focuses on RISC-V architecture porting. In fact, the tool may have an average estimate of various architecture porting efforts.My focus is on the overall workload and difficulty of transplantation in the past and future,even if a project has already been ported.As part of my dataset, I have collected the xen project. I would like to gather community opinions to support my assessment. I appreciate your help and response! Based on scanning tools, the porting complexity is determined to be high, with a moderate amount of code related to the CPU architecture in the project. Is this assessment accurate?Do you have any opinions on personnel allocation and consumption time? I look forward to your help and response.
-
Hi,
We are already working on porting Xen to RISC-V.
See:
- https://xcp-ng.org/blog/2021/03/12/xen-and-the-risc-v-hypervisor-extension/
- https://xcp-ng.org/blog/2023/02/07/current-xen-risc-v-support-status/
- https://xcp-ng.org/blog/2023/05/23/new-xen-updates-on-risc-v/
However, we'll be happy to have some assistance. It's a pure "upstream" work. Assistance can be more people or more money to get more resources on it
-
@olivierlambert Thank you for the information you provided, can you give some more specific comments? Our tool classifies a project's porting complexity into three levels: easy, medium, and hard. Do you think the xen transplantation process is difficult? What problems have you encountered? In what aspects is the work mainly carried out, and what kind of manpower, funds and time are consumed? Looking forward to your further reply. Thanks!
-
Well, it's not really possible to answer with a short answer. Globally, for the whole platform, we are talking about hard in a way that it takes time.