Hi all, since Paolo recently suggested to decrease the bus factor for kvm-unit-tests [1], I suggested (in a private mail) to maybe also move the repo to one of the git forges where we could benefit from a CI system (so that we do not merge bugs so often anymore as it happened in the previous months). If we do that step, that might be a good point in time to rename the kvm-unit-tests to something more adequate. "Why?" you might ask ... well, the unit tests are not only useful for kvm anymore: - They can also be used for testing TCG in QEMU - There have been attempts in the past to use them for OpenBSD [2] - They can be used for hvf on macOS now [3] - The s390x tests can also be run with the z/VM and LPAR hypervisors - Some people also try to run certain tests on x86 bare metal (for comparing the behavior of virtual CPUs with real CPUs) Liran already suggested the name "cpu-unit-tests" a while ago [4], which is certainly a better description of what the tests are doing nowadays. But I wonder whether that name is maybe too generic? For example, if someone does not know that there should be dashes in between and just searches for "cpu unit tests" with their favorite search engine, would they find the right project site? Maybe we should come up with a more fancy name for the test suite? For example something like "HECATE" - "*H*ypervisor *E*xecution and *C*pu instruction *A*dvanced *T*est *E*nvironment" (and Hecate is also the goddess of boundaries - which you could translate to the hypervisor being the boundary between the virtual and real machine ... with a little bit of imagination, of course) ... well, yeah, that's just what came to my mind so far, of course. Let's brainstorm ... do you have any good ideas for a new name of the kvm-unit-tests? Or do you love the old name and think it should stay? Or do you think cpu-unit-tests would be the best fit? Please let us know! Thanks, Thomas [1] https://lore.kernel.org/kvm/e79b76ae-c554-6d28-7556-88b280b8f02f@xxxxxxxxxx [2] https://patchwork.kernel.org/patch/9625205/#20244627 [3] https://lore.kernel.org/kvm/20200320145541.38578-3-r.bolshakov@xxxxxxxxx/ [4] https://patchwork.kernel.org/patch/11260891/#23021859
