Wow, that's fantastic. The best thing you can do is get your code working with the new repository using mercurial and mercurial queues. If you do that, then we can work with you to make sure that the code meets all of the requirements (doesn't break things, is reasonably organized, meets the style guidelines, etc.)
Did you use a revision control system as you did your work? Thanks, Nate 2008/7/11 jiayuan meng <[EMAIL PROTECTED]>: > Dear all, > > I appreciate all your support to help me with M5. I really love it. I'm > a graduate student working with Prof. Kevin Skadron at University of > Virginia. And now, > I'd like to submit patches to M5 that enables it to simulate CMP > architecture. > > I have a mesh2D model that works well with an MSI directory coherence > protocol. > Both the interconnection and directory coherence models are extendable. > Another patch is to support multithreading for simple CPUs. The cpu can > switch to another HW thread context if it has a data access. > > However, atomic modes are not well tested. And I haven't considered > checkpoints. > > The mercurial patches are based on changeset 5291:456a50cf2a67, a version > after 2.0beta4 but before 2.0beta5. > As an "external developer", how do you think I should submit the patches? An > do you think it would be necessary to update the patches so they are based > on a more recent changeset? > If so, which changeset? > > Just hope it might be useful. > > Thanks! > > Jiayuan Meng > > ________________________________ > Need to know now? Get instant answers with Windows Live Messenger. IM on > your terms. > _______________________________________________ > m5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/m5-dev > > _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
