MEM: VirtualPorts are replaced with FSTranslatingProxys
Review Request #919 - Created Nov. 28, 2011 and discarded
| Information | |
|---|---|
| Andreas Hansson | |
| gem5 | |
| default | |
| Reviewers | |
| Default | |
| ali, gblack, nate, stever | |
MEM: VirtualPorts are replaced with FSTranslatingProxys This patch introduces the FSTranslatingProxy instances replacing the VirtualPorts. This requires small chagnes to many files. Some functionality (object loading) in constructors of System and derived objects have been moved to the initState methods instead. This method is called after the interconnections has been established, therefore the PortProxies are functioning.
util/regress passing all ignoring failing eio and t1000
Posted (Dec. 3, 2011, 1:10 a.m.)
-
src/arch/arm/system.cc (Diff revision 1) -
It's pretty minor, but why not just add a line: Params *p = params(); and then you wouldn't have to make all the separate changes below? -
src/base/remote_gdb.cc (Diff revision 1) -
Notice that in the original code the port->readBlob() was factored out of the #if, but now the readMem() call is not. Ideally we should be able to do this: TranslatingProxy *port = context->getVirtProxy(); port->readMem(...); and have it work in both SE and FS mode with no #if at all.
-
tests/configs/t1000-simple-atomic.py (Diff revision 1) -
I don't even see this line in the current code, so I'm assuming this is some kind of glitch with reviewboard.
