Another small project:
Unify PS/2 handling: PS2 is implemented by both the i8042 and PL050
models, but almost no code is shared.
//Andreas
On 23/01/17 15:57, Andreas Sandberg wrote:
Hi Everyone,
Thanks for organising this! See below for some of my ideas.
Small projects:
* Clean up serialization code for better code reuse (particularly
container helpers)
* Create a separate test classification for CI smoke tests (faster
than quick)
Medium-sized projects:
* New test binaries based on the LLVM test suite
* Mini-DSL for param overrides from the command line
* Config cleanups. E.g., move some of config/common/ to a m5.config
name space.
* Proper support for pthreads in SE mode
* Implement a fast mode in the HDLCD controller to support graphical
worklaods (e.g., Android) in KVM
Large projects:
* Get scons to build basic components only once and share them
between architectures
I'd like to throw cmake in to the build system mix as well. I started
hacking on a small prototype a while back, but it isn't able to build
gem5 yet.
Cheers,
Andreas
On 17/01/17 16:12, Jason Lowe-Power wrote:
Hi gem5 Developers!
As you're probably aware, I'm going to be running a gem5 coding
sprint in
the afternoon after the Learning gem5 tutorial at HPCA on Sunday Feb 5.
I'm looking for ideas for small projects that could be started (or even
better, completed) in a few hours. Do you have any small bugs that have
been bothering you? Any little features that would be nice, but you
haven't
had the time to work on? Now's the time to get these things done!
Also, if you have any bigger projects that you think it would be good
for
people to chat about in the same room to come up with a plan of
attack, we
may be able to fit one or two of those in, too.
Some examples that I have so far:
Little projects:
1. Fix TLB warmup for x86. (See http://reviews.gem5.org/r/3474/)
2. Modify EventWrapper to understand C++11 lambdas so you can pass
parameters to simple process() functions without creating a new class.
3. Develop some ISA instruction tests to find out what is implemented
correctly and possibly find some bugs. (See RISC-V insttest)
Long-term things we may want to discuss:
1. Revamping the test infrastructure
2. Replacing scons, possibly with Bazel (see https://bazel.build/)
Please respond with any ideas you have! We definitely won't get to
everything, but throwing ideas out there now will give us a large
base of
options for the coding sprint.
Thanks,
Jason
IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended
recipient, please notify the sender immediately and do not disclose
the contents to any other person, use it for any purpose, or store or
copy the information in any medium. Thank you.
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev
IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended recipient,
please notify the sender immediately and do not disclose the contents to any
other person, use it for any purpose, or store or copy the information in any
medium. Thank you.
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev
