On Wed, Mar 30, 2016 at 6:33 PM, Nashif, Anas <anas.nashif(a)intel.com> wrote:
On 30/03/2016, 11:52, "Benjamin Walsh" <benjamin.walsh(a)windriver.com> wrote:
You can post the patch and add me for review. From what I've seen, there's ~10 tests that fail under sanitycheck with SRAM overflow from hundreds of bytes, to couple of kBs. My idea was to go through the failing ones and see if it's possible trim the amount of memory required in the manner similar to what was done to the latency benchmarks. If that's not possible, the test will get disabled for this particular target.
Now that I've seen the patch it got me thinking. What if we added an opt-in debug code for fiber/tasks that helped to measure stack usage? This could be something really simple, like initializing the stack area with some known pattern (ex. '.') and once the fiber/task is
That part is already in the kernel: CONFIG_INIT_STACKS fills the stacks with 0xaa when threads are initialized.
also look at
include/misc/stack.h
for Stack usage analysis helpers
Thanks. Looks like we have everything in place then.
