I'm not sure what 'typical' usage of M5 looks like, but I for one spend a lot of time understanding the existing code (both C++ and Python) in order to modify / extend it -- as opposed to either using it as is or writing entirely new code. I think more emphasis in a tutorial on how to use M5 in that capacity (and less on history / overview) would be helpful.
I personally wasn't familiar with Python, so I had to spend a lot of time understanding (relatively simple) Python code -- for example, the code provided in se.py or fs.py -- in order to change it to suit my needs. It would be great if you could cover the basics of the Python infrastructure -- and perhaps use one of those files as part of the example (since they are likely the most commonly used Python files, from a user perspective). Echoing Philip's suggestion, perhaps the 'complete example' he suggests could be a 'How to' for a (simple) modification to the existing code? You wouldn't need to actually dwell on the details of the new feature, but it would allow you to highlight a variety of areas in the simulator in the process. -Vilas On Feb 11, 2008 12:35 AM, Philip Machanick <[EMAIL PROTECTED]> wrote: > I took a quick look at the ISCA 2006 tutorial and it reads well as an > overview of a manual but a complete example including a good fraction > (obvious not all) of the features at the end would be a useful > addition to put it all together. > > A possible approach: use pieces of this complete example to introduce > the features, then go over the whole thing at the end. > > On 2/11/08, Ali Saidi <[EMAIL PROTECTED]> wrote: > > Everyone, > > > > Below is roughly the outline we've used for previous M5 tutorials. > > We're in the process of updating our slides for the ASPLOS tutorial in > > a few weeks and would like any input you have. Irrespective of if you > > plan to attend the tutorial or not we would like input about what > > should be covered in more detail and what we're spending too much time > > on. > > > > Thanks, > > Ali > > > > > > Introduction & Overview > > History > > Attributes > > Objects/Events/Modes > > Current work (lots has change) > > Future Work (lots has changed) > > Compiling and Running M5 > > Source Tree > > Building > > Output files > > Checkpoints > > Simpoints > > Full system workloads > > Network workloads > > Parts of a workload > > Current M5 Object models > > CPU Models > > Time buffers > > Templates > > Checker > > State > > Memory System > > Requests/Packets > > Access modes > > Interconnects > > Caches > > Coherence > > I/O > > Device overview > > Disks > > NICs > > Extending M5 > > M5 Internals > > Configurations > > Serialization > > Events > > ISA description > > Statistics > > Debugging M5 > > Tracing > > Debugger > > Remote debugger > > Wrapup > > _______________________________________________ > > m5-users mailing list > > m5-users@m5sim.org > > http://m5sim.org/cgi-bin/mailman/listinfo/m5-users > > > > > -- > Philip Machanick (Visiting Fellow, School of ITEE, University of > Queensland) > 39 Cunningham Street, Taringa, Qld 4068, Australia > http://opinion-nation.blogspot.com/ > +61-7-3871-0963 (office 3365-1190) skype philipmach > _______________________________________________ > m5-users mailing list > m5-users@m5sim.org > http://m5sim.org/cgi-bin/mailman/listinfo/m5-users >
_______________________________________________ m5-users mailing list m5-users@m5sim.org http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
