This graph shows some of the function calls that gem5 makes when it starts up when running the "Hello, World" example that comes with the project. These are the function calls that I found most significant in understanding what it is doing, including those calls that lead to the construction of the objects used by the simulator.
The edge labels show the names of the functions that are being called, and the node labels show the names of the files containing the function named on the incoming edge.
I believe this should cover the basics of the graph (except for the "filecode <= arguments[0]", which I think is just showing that the "filecode" variable is getting assigned in src/python/m5/main.py. I'm not sure why I noted this in this way. Sorry that this is not clear.)
Please let me know if there are any other questions you think I might be able to answer.
Can you explain this graph a little bit?
ReplyDeleteKumail, sorry for the delay in my response.
DeleteThis graph shows some of the function calls that gem5 makes when it starts up when running the "Hello, World" example that comes with the project. These are the function calls that I found most significant in understanding what it is doing, including those calls that lead to the construction of the objects used by the simulator.
The edge labels show the names of the functions that are being called, and the node labels show the names of the files containing the function named on the incoming edge.
I believe this should cover the basics of the graph (except for the "filecode <= arguments[0]", which I think is just showing that the "filecode" variable is getting assigned in src/python/m5/main.py. I'm not sure why I noted this in this way. Sorry that this is not clear.)
Please let me know if there are any other questions you think I might be able to answer.