From 73882a2bcc19432c18e951eadc1f212fb4fed24b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ciro=20Santilli=20=E5=85=AD=E5=9B=9B=E4=BA=8B=E4=BB=B6=20?= =?UTF-8?q?=E6=B3=95=E8=BD=AE=E5=8A=9F?= Date: Tue, 29 Oct 2019 00:00:00 +0000 Subject: [PATCH] gem5 entry point: expand a bit more to mention m5.simulate() --- README.adoc | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/README.adoc b/README.adoc index 460dab6..c8cef05 100644 --- a/README.adoc +++ b/README.adoc @@ -12768,6 +12768,14 @@ exec filecode in scope TODO: the file path name appears to be passed as a command line argument to the Python script, but I didn't have the patience to fully understand the details. +The Python config files then set the entire system up in Python, and finally call `m5.simulate()` to run the actual simulation. This function has a C++ native implementation at: + +.... +src/sim/simulate.cc +.... + +and that is where doSimLoop the main event loop, `doSimLoop` gets called and starts kicking off the <>. + Tested at gem5 b4879ae5b0b6644e6836b0881e4da05c64a6550d. ==== gem5 event queue