On Fri, 20 Nov 2015 15:23:09 -0800 (PST) David Rientjes <rientjes@xxxxxxxxxx> wrote: > On Fri, 20 Nov 2015, Jesper Dangaard Brouer wrote: > > > > Any chance you could proffer some of your scripts in the form of patches > > > to the tools/testing directory? Anything that can reliably trigger rarely > > > executed code is always useful. > > > > Perhaps that is a good idea. > > > > I think should move the directory location in my git-repo > > prototype-kernel[1] to reflect this directory layout, like I do with > > real kernel stuff. And when we are happy with the quality of the > > scripts we can "move" it to the kernel. (Like I did with my pktgen > > tests[4], now located in samples/pktgen/). > > > > A question; where should/could we place the kernel module > > slab_bulk_test04_exhaust_mem[1] that my fail01 script depends on? > > > > I've had the same question because I'd like to add slab and page allocator > benchmark modules originally developed by Christoph Lameter to the tree. > Let's add Andrew. Well, fwiw the current approach is to build the testing module in lib/ (ls -l lib/*test*.c) and to modprobe it from selftests (grep -r modprobe tools/testing/selftests). Does that suit? I guess we could build and install a module from mm/ if that's needed for some reason. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>