On Mon, Nov 3, 2008 at 4:45 PM, Subrata Modak <[EMAIL PROTECTED]> wrote: > > On Mon, 2008-11-03 at 10:24 +0800, Peter Teoh wrote: >> i would like to test all the system calls available in Linux currently. >> >> Is there a way for me to "make menuconfig" and select which system >> calls I want to test, or perhaps any other kernel features to test, >> and then "make" to continue generation of the scripts/binaries to >> continue the testing. > > No, we do not have things like that. > >> >> does it make sense to have such a feature if it is not available right now? > > Let us know how you would like to do that. >
the easiest way, i think, is to: 1. create a subdirectory called "LTP" directly at the root directory of the kernel source tree. then unpack the entire LTP packages there. and since the existing kernel source's "make menuconfig" require a Kconfig + Makefile, we will create one in LTP subdirectory. 2. make it automatic, such that whenever any of the LTP option is chosen, its corresponding required/dependent kernel features is also chosen. this will thus enable an integrated testing possible. ie, each of the required LTP test cases chosen, will be guaranteed to have the corresponding kernel features chosen, and "make" will generate a testable "vmlinux" images for testing. 3. (this is much farther, but good enhancement) if possible, another extension to the "make menuconfig", again under the LTP branch, will be different choices of using QEMU, or UML to test the kernel APIs etc. (eg after "make", issue "make test qemu" or "make test uml", which will generate the rootfs, or supplying necessary parameters for testing). The advantage of this, is that by supplying "make randconfig" it is possible to test as much of the kernel features in userspace, and upon completion, will loop again to "make randconfig" to generate a new .config and thus vmlinux, as well as its corresponding test cases. Thus test automation is possible. Since we are using the kernel source's make script infrastructure, there is minimal work needed. And all enhancement/modifications to the make scripts infrastructure, should be made out of the kernel source tree, possible residing in LTP's tree. Comments? >> >> moreover, like the case of "make randconfig", which easily allows for >> automatic testing based on infinitely generating different version of >> .config file, it will be good to incorporate such feature of "fuzzing" >> into existing test scripts/C programs, so that a autofeeder will >> generate different combinations of parameters and used by the test >> scripts/C programs. >> >> comments? > > Regards-- > Subrata > >> > > -- Regards, Peter Teoh ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
