Tim, > I've got a simple Barrelfish system now running. It gets as far as booting 1 > core, starting various system processes on them, and running a user-mode test > app. My current changes are a mess -- both the changes to m5 and to > Barrelfish -- so I'll need to go back and do it properly, but I've got far > enough to confirm that there aren't any major problems.
This is all great stuff. I personally am quite excited that Barrelfish may someday be a supported OS by M5. My personal preference would be to incorporate your changes into the M5 codebase (hopefully that is your intent). Assuming that is what you want (though I don't know that it truly matters), once you feel comfortable sharing your patches, please put them on http://reviews.m5sim.org for comments. Initially, we can comment on the general approach. When you're actually getting ready to commit, then we'll start to nitpick. :) As a side comment to help your efforts, you should check out our page on debugging. It's mostly up to date (though it's not complete). One thing of particular interest for you going down the road might be our remote debugger support. I'm not sure what the status of x86 remote debugging is, but in general, remote debugging with M5 is quite nice because it is controlled by M5 outside of the running system. The major implication of this is that you can step through (and set breakpoints in) just about any code. On alpha at least, I used it to step through interrupt handlers and low level platform code. http://m5sim.org/wiki/index.php/Debugging_M5 Nate _______________________________________________ m5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
