90 likes | 230 Views
Conclusions. Ali Saidi. Thank You!. Great attendance today 53+ people Community is requirement to sustain gem5 No one company or person can do it Impressive breadth of work Different ways of doing things Success stories but also what we could do better. After You Leave….
E N D
Conclusions Ali Saidi
Thank You! • Great attendance today • 53+ people • Community is requirement to sustain gem5 • No one company or person can do it • Impressive breadth of work • Different ways of doing things • Success stories but also what we could do better
After You Leave… • Please continue these discussions • Throughout the conference • On the mailing list • Progress them further • Lots of great talks that have changes not in gem5 • Please commit them • You might get back more than you put in
Discussion Topics • Review Process / Encouraging Participation – Back Left • Verification/Validation – Front Left • Ease of use/Documentation – Back Right • Clean-up -- Forward Right
Review Process / Encouraging Participation • How do we encourage more participation? • More people are using and changing gem5 than are committing • What can tooling help with? • Review cost/benefit trade-off? • Governance • Jason Power
Clean-up • Functional Model should be faster? • Are we carrying too much cruft? • APIs kind of broken • Multiple functions doing same thing • Alex Dutu
Verification/Validation • A new regression system? • How to enable better and easier testing? • Publically available binaries • Fewer of the same tests • Integration with other tools • Andreas Hansson
Ease of use/Documentation • Making config system easier to use • Split assembly, configuration and orchestration? • Auto-generating OS tables (e.g. DTB) • Running elaborate workloads • Kassan