Bug 6941

Summary: microLinux: Automatic code elimination
Product: [Build System, Metadata & Runtime] Meta-yocto Reporter: Tom Zanussi <tom.zanussi>
Component: meta-yoctoAssignee: Tom Zanussi <tom.zanussi>
Status: RESOLVED OBSOLETE QA Contact:
Severity: normal    
Priority: Undecided CC: jessica.zhang, poky.bs.watcher, poky.watcher
Version: 1.8   
Target Milestone: 1.8 M4   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know

Description Tom Zanussi 2014-11-07 21:07:57 UTC
One important use case of microLinux is the size minimization of dedicated single-purpose embedded systems.  In cases like that, it should be possible to apply various techniques to exhaustively determine which code paths will and will not ever be executed on such a system.

This is actually a superset of 'automatic syscall elimination' but recognizes that there's nothing special about syscalls in this respect - all kernel code should be subject to these techniques.

I think some of the existing dynamic tracing infrastructure as well as some refactoring and reuse of certain parts of the hash triggers patchset could be applied to this problem.

In my ELC talk, I called this 'Trace Guided Optimization' - basically the application of tracing techniques to optimize out unused parts of a given single-purpose system.
Comment 1 Jessica 2015-02-09 23:59:38 UTC
MicroLinux is moved out of project