On 12.09.2017 18:43, Paolo Bonzini wrote: > On 12/09/2017 18:39, David Hildenbrand wrote: >> >>>> Hmm.... probably have too look into the details of the malloc discussion... >>> >>> It's really less work than it sounds. I'm not wed to GTest, but I think >>> the ability to define test cases programmatically is useful (vmexit.c >>> for example has a case where the testcase list is actually in QEMU!) and >>> it pretty much requires malloc. >> >> Btw, by "has a case where the testcase list is actually in QEMU" you >> mean simply selecting the list of tests to run via -apend? > > No, QEMU has a test device that can provide the names of several > testcases. So you could have a test named "name_of_test1" but > name_of_test1 is actually not in kvm-unit-tests, it is in QEMU. > > Paolo > >> This is already supported in this current RFC, and the way Thomas >> implemented it doesn't require malloc - see "run_it". (it's not 100% >> clean but for our purpose just ok). >> pci-testdev (I learned something today :)). Got it, basically dynamically adding tests. -- Thanks, David
