development []

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
===== Ongoing gem5-gpu Development =====
  * Join the gem5-gpu-dev email list by requesting [[https://groups.google.com/forum/?fromgroups#!forum/gem5-gpu-dev|access]].
  * To encourage ongoing gem5-gpu development, we are hosting a code review site at [[http://multifacet-reviews.cs.wisc.edu/]]
    * To gain access to the reviews site, please first request access to our email list above, and then send email to ***Marc?*** for approval to create a reviews account. You will need “reviews user ID” below.
    * We plan to use a review and commit process very similar to gem5 ([[http://gem5.org/Commit_Access]])
    * Setup:
      * Since gem5-gpu spans 3 separate codebases (gem5, GPGPU-Sim, and gem5-gpu), there are 3 separate repositories to which you will need to submit code reviews
      * First, you’ll need to configure Mercurial to point to appropriate repo IDs for submitting patches to gem5-patches, gpgpu-sim-patches and gem5-gpu repos. Add the following Reviewboard configuration to the listed Mercurial config files:
        * gem5-gpu/gem5/.hg/hgrc (repoid = 6)
        * gem5-gpu/gpgpu-sim/.hg/hgrc (repoid = 7)
        * gem5-gpu/gem5-gpu/.hg/hgrc (repoid = 8)


<code>
[reviewboard]
server          = https://multifacet-reviews.cs.wisc.edu/
user            = <reviews user ID>
repoid          = <IDs listed above>
</code>

**NOTE: If you setup GPGPU-Sim from the public git server instead of pulling from our repositories, you will not be able to submit review requests to our GPGPU-Sim patches repository**

      * To submit a code review to gem5 or GPGPU-Sim, create a new patch at the tip of the patch queue containing your changes. Use hg postreview -o in either the gem5 or GPGPU-Sim repository (NOT the patch repository) to submit this patch for review. Checking in this code will require that you push a patch to the appropriate patch queue rather than to the gem5 or GPGPU-Sim repositories. This process may require merging your patch with prior patches in the queue.
      * To submit a code review to gem5-gpu, simply create a patch using Mercurial queues and submit it using hg postreview -o. To check in this patch, use hg qfinish to commit the patch to your local repository, and then use hg push to check the code into the mainline repository.

**NOTE: Publishing changesets is currently only supported with UW CS credentials, but details for pushing to the mainline repository will be updated as secure, open publishing becomes available.**

    * Simulation control and regression:
      * We have setup a simple tool for organizing, running and regressing simulations. We can make this tool available assuming there is demand for it, but the gem5 regressions structure is being updated in their public release, and we would like to wait on these updates before releasing a structured set of regressions. In the meantime, patches submitted for review will be applied and regressed internally at UW before a “Ship it!” will be applied.

      * The repo for the control tool can be cloned as follows:

            cd /path/to/gem5-gpu
            hg clone <<gem5-gpu/pub>>/regressions

      * The script that controls simulation runs is regressions/regress.py
User Tools

Site Tools

Page Tools
