Config: Add ruby_fs.py's functionality to fs.py
Review Request #818 - Created Aug. 5, 2011 and discarded
| Information | |
|---|---|
| Nilay Vaish | |
| gem5 | |
| default | |
| Reviewers | |
| Default | |
Config: Add ruby_fs.py's functionality to fs.py This patch combines fs.py and ruby_fs.py and removes ruby_fs.py. Using ruby with fs.py would require mentioning --ruby on the command line. This same as se.py.
Posted (Aug. 9, 2011, 2:07 a.m.)
I just have a couple minor edits to make to the comments. However, I wonder what is the real benefit for combining the two fs files. I don't believe there is a lot of duplicate code between the two. Most of the added options in fs.py are not supported/related to Ruby. Also with your change, the main body of fs.py is now a large if/else statement with the if being the functionality from ruby_fs.py and the else being the fs.py functionality. Overall, I feel this is an unnecessary change that will negatively impact those of us who have other internal patches that modify these files. Why do it?
-
configs/example/fs.py (Diff revision 1) -
Remove "ALPHA_FS" from comment. Ruby now works with both ALPHA and X86.
-
configs/example/fs.py (Diff revision 1) -
Change comment to say the driver system is always atomic with the Classic memory system.
