Re: [gem5-dev] Ideas for sprint projects
I honestly don't know much about bazel. I heard that it has or is going to have tightly integrated support for testing and continuous integration. I only brought it up to start a conversation :). Given that bazel isn't going to be out of beta until at least Q4 2017, it's likely that we should stick with something more stable for the time being. ( https://bazel.build/roadmap.html) The main reason I bring it up is that I'd hate for someone to spend a month re-writing our build system for cmake, only to have to re-write it again for the next "best" build system in a few years. Cheers, Jason On Fri, Jan 27, 2017 at 4:07 PM Cagdas Dirik (cdirik) wrote: > Thank you for putting them together Jason! > > One quick question - regarding "replacing scons...". Is there a specific > reason for stepping over cmake and jumping to bazel? It feels to me > "replacing scons with cmake" will be more beneficial (assuming cmake is > more common for gem5 developers than bazel). > > Cagdas > > -Original Message- > From: gem5-dev [mailto:gem5-dev-boun...@gem5.org] On Behalf Of Jason > Lowe-Power > Sent: Thursday, January 26, 2017 12:41 PM > To: gem5 Developer List > Subject: Re: [gem5-dev] Ideas for sprint projects > > Thanks everyone who came up with some ideas! > > I've compiled them on this page on the wiki: http://gem5.org/Sprint_Ideas. > Feel free to edit or add more ideas. I tried to expand on each idea with a > few sentences, but I didn't get to all of them. I also included the person > who suggested the idea with it. > > Cheers, > Jason > > On Wed, Jan 25, 2017 at 12:02 PM Andreas Hansson > wrote: > > > Hi all, > > > > A large-sized project for some crafty person out there: A > > binary-translation CPU for fast-forwarding, much like the KVMCpu, but > > more portable. It could, for example, be built on top of the Tiny Code > > Generator (TCG), as it is BSD licensed. > > > > Quite a big task, but also a very big contribution to gem5. > > > > Andreas > > > > On 23/01/2017, 16:57, "gem5-dev on behalf of Andreas Hansson" > > wrote: > > > > >Hi all, > > > > > >Another medium-sized idea: Embed the generated system SVG in a web > > >page that can be used to interactively navigate the simulation > > >results > > > > > >This should be fairly easy for anyone skilled in client-side > > >scripting. It may even be used to view incremental results while the > > >simulation is running. > > > > > >Andreas > > > > > >On 23/01/2017, 15:57, "gem5-dev on behalf of 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 bug
Re: [gem5-dev] Ideas for sprint projects
Thank you for putting them together Jason! One quick question - regarding "replacing scons...". Is there a specific reason for stepping over cmake and jumping to bazel? It feels to me "replacing scons with cmake" will be more beneficial (assuming cmake is more common for gem5 developers than bazel). Cagdas -Original Message- From: gem5-dev [mailto:gem5-dev-boun...@gem5.org] On Behalf Of Jason Lowe-Power Sent: Thursday, January 26, 2017 12:41 PM To: gem5 Developer List Subject: Re: [gem5-dev] Ideas for sprint projects Thanks everyone who came up with some ideas! I've compiled them on this page on the wiki: http://gem5.org/Sprint_Ideas. Feel free to edit or add more ideas. I tried to expand on each idea with a few sentences, but I didn't get to all of them. I also included the person who suggested the idea with it. Cheers, Jason On Wed, Jan 25, 2017 at 12:02 PM Andreas Hansson wrote: > Hi all, > > A large-sized project for some crafty person out there: A > binary-translation CPU for fast-forwarding, much like the KVMCpu, but > more portable. It could, for example, be built on top of the Tiny Code > Generator (TCG), as it is BSD licensed. > > Quite a big task, but also a very big contribution to gem5. > > Andreas > > On 23/01/2017, 16:57, "gem5-dev on behalf of Andreas Hansson" > wrote: > > >Hi all, > > > >Another medium-sized idea: Embed the generated system SVG in a web > >page that can be used to interactively navigate the simulation > >results > > > >This should be fairly easy for anyone skilled in client-side > >scripting. It may even be used to view incremental results while the > >simulation is running. > > > >Andreas > > > >On 23/01/2017, 15:57, "gem5-dev on behalf of 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
Re: [gem5-dev] Ideas for sprint projects
Thanks everyone who came up with some ideas! I've compiled them on this page on the wiki: http://gem5.org/Sprint_Ideas. Feel free to edit or add more ideas. I tried to expand on each idea with a few sentences, but I didn't get to all of them. I also included the person who suggested the idea with it. Cheers, Jason On Wed, Jan 25, 2017 at 12:02 PM Andreas Hansson wrote: > Hi all, > > A large-sized project for some crafty person out there: A > binary-translation CPU for fast-forwarding, much like the KVMCpu, but more > portable. It could, for example, be built on top of the Tiny Code > Generator (TCG), as it is BSD licensed. > > Quite a big task, but also a very big contribution to gem5. > > Andreas > > On 23/01/2017, 16:57, "gem5-dev on behalf of Andreas Hansson" > wrote: > > >Hi all, > > > >Another medium-sized idea: Embed the generated system SVG in a web page > >that can be used to interactively navigate the simulation results > > > >This should be fairly easy for anyone skilled in client-side scripting. It > >may even be used to view incremental results while the simulation is > >running. > > > >Andreas > > > >On 23/01/2017, 15:57, "gem5-dev on behalf of 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 > >>gem5-dev@gem5.org > >>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 > >gem5-dev@gem5.org > >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
Re: [gem5-dev] Ideas for sprint projects
Hi all, A large-sized project for some crafty person out there: A binary-translation CPU for fast-forwarding, much like the KVMCpu, but more portable. It could, for example, be built on top of the Tiny Code Generator (TCG), as it is BSD licensed. Quite a big task, but also a very big contribution to gem5. Andreas On 23/01/2017, 16:57, "gem5-dev on behalf of Andreas Hansson" wrote: >Hi all, > >Another medium-sized idea: Embed the generated system SVG in a web page >that can be used to interactively navigate the simulation results > >This should be fairly easy for anyone skilled in client-side scripting. It >may even be used to view incremental results while the simulation is >running. > >Andreas > >On 23/01/2017, 15:57, "gem5-dev on behalf of 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 >>gem5-dev@gem5.org >>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 >gem5-dev@gem5.org >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 gem5-dev@gem5.org http://m5sim.org/mailman/listinfo/gem5-dev
Re: [gem5-dev] Ideas for sprint projects
Here are some ideas we at AMD have for the sprint. 1) Adding checkpointing support to the GPU model 2) Fixing the structure and design of the GPU coalescer 3) Adding x86 inst tests 4) Properly supporting atomics 5) Add support for event-based scheduling in the GPU model, and FUPool-style functional units -Original Message- From: gem5-dev [mailto:gem5-dev-boun...@gem5.org] On Behalf Of Jason Lowe-Power Sent: Tuesday, January 17, 2017 8:13 AM To: gem5 Developer List Subject: [gem5-dev] Ideas for sprint projects 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 -- Jason ___ gem5-dev mailing list gem5-dev@gem5.org http://m5sim.org/mailman/listinfo/gem5-dev ___ gem5-dev mailing list gem5-dev@gem5.org http://m5sim.org/mailman/listinfo/gem5-dev
Re: [gem5-dev] Ideas for sprint projects
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 gem5-dev@gem5.org 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 gem5-dev@gem5.org http://m5sim.org/mailman/listinfo/gem5-dev
Re: [gem5-dev] Ideas for sprint projects
Hi all, Another medium-sized idea: Embed the generated system SVG in a web page that can be used to interactively navigate the simulation results This should be fairly easy for anyone skilled in client-side scripting. It may even be used to view incremental results while the simulation is running. Andreas On 23/01/2017, 15:57, "gem5-dev on behalf of 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 >gem5-dev@gem5.org >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 gem5-dev@gem5.org http://m5sim.org/mailman/listinfo/gem5-dev
Re: [gem5-dev] Ideas for sprint projects
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 gem5-dev@gem5.org http://m5sim.org/mailman/listinfo/gem5-dev
[gem5-dev] Ideas for sprint projects
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 -- Jason ___ gem5-dev mailing list gem5-dev@gem5.org http://m5sim.org/mailman/listinfo/gem5-dev
