Sending a patch to linux-mm today has become a complex task. One of the reasons for the complexity is a lack of fundamental expectation of what tests to run. Mel Gorman has a set of tests [1], but there is no easy way to select what tests to run. Some of them are proprietary (spec*), but others have varying run times. A single line change may require hours or days of testing, add to that complexity of configuration. It requires a lot of tweaking and frequent test spawning to settle down on what to run, what configuration to choose and benefit to show. The proposal is to have a discussion on how to design a good sanity test suite for the mm subsystem, which could potentially include OOM test cases and known problem patterns with proposed changes It would be great if we could discuss that in the summit this time, all members are welcome and encouraged to participate. References: [1] https://github.com/gormanm/mmtests
