On 23/01/2020 05:19, Bobby Eshleman wrote: > On Wed, Jan 22, 2020 at 02:57:47PM +0000, Andrew Cooper wrote: >> How much time do you have to put towards the port? Is this something in >> your free time, or something you are doing as part of work? Ultimately, >> we are going to need to increase the level of RISC-V knowledge in the >> community to maintain things in the future. >> > This is something in my free time, and I have about 20 hours a week to > put into it.
Ok, so not full time, but hopefully enough time to help spread some knowledge. > >> Other than that, very RFC series are entirely fine. A good first step >> would be simply to get the build working, and get some kind of >> cross-compile build in CI, to make sure that we don't clobber the RISC-V >> build with common or other-arch changes. >> > That's something I can look at, if the idea of QEMU in CI is > not too horrific. We have https://gitlab.com/xen-project/xen/pipelines which runs a load of containerised builds. How easy is it to set up a containerised RISC-V cross-compiler environment? The test step also boots Xen under Qemu software emulation to check that we don't have any boot-time screamers. A reasonable second step might be to have start_xen() panic() at the end, and check for that in the console log, which would allow for some kind of boot testing before getting all the way to "and here is dom0 ready to run". All configuration is in .gitlab-ci.yml and automation/. ~Andrew _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
