gem5/util/systemc/gem5_within_systemc at 974a47dfb9f67d597fb2c9d09eea5d78ee14702b - gem5

derek/gem5

Files

Daniel R. Carvalho 974a47dfb9 misc: Adopt the gem5 namespace

Apply the gem5 namespace to the codebase.

Some anonymous namespaces could theoretically be removed,
but since this change's main goal was to keep conflicts
at a minimum, it was decided not to modify much the
general shape of the files.

A few missing comments of the form "// namespace X" that
occurred before the newly added "} // namespace gem5"
have been added for consistency.

std out should not be included in the gem5 namespace, so
they weren't.

ProtoMessage has not been included in the gem5 namespace,
since I'm not familiar with how proto works.

Regarding the SystemC files, although they belong to gem5,
they actually perform integration between gem5 and SystemC;
therefore, it deserved its own separate namespace.

Files that are automatically generated have been included
in the gem5 namespace.

The .isa files currently are limited to a single namespace.
This limitation should be later removed to make it easier
to accomodate a better API.

Regarding the files in util, gem5:: was prepended where
suitable. Notice that this patch was tested as much as
possible given that most of these were already not
previously compiling.

Change-Id: Ia53d404ec79c46edaa98f654e23bc3b0e179fe2d
Signed-off-by: Daniel R. Carvalho <odanrc@yahoo.com.br>
Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/46323
Maintainer: Bobby R. Bruce <bbruce@ucdavis.edu>
Reviewed-by: Bobby R. Bruce <bbruce@ucdavis.edu>
Reviewed-by: Matthew Poremba <matthew.poremba@amd.com>
Tested-by: kokoro <noreply+kokoro@google.com>

2021-07-01 19:08:24 +00:00

main.cc

misc: Adopt the gem5 namespace

2021-07-01 19:08:24 +00:00

Makefile

util: Delete authors lists from files in util.

2020-02-18 10:24:43 +00:00

README

systemc: Update the gem5-within-systemc README to mention USE_SYSTEMC.

2018-11-29 08:50:52 +00:00

sc_gem5_control.cc

misc: Adopt the gem5 namespace

2021-07-01 19:08:24 +00:00

sc_gem5_control.hh

misc: Adopt the gem5 namespace

2021-07-01 19:08:24 +00:00

sc_logger.cc

misc: Adopt the gem5 namespace

2021-07-01 19:08:24 +00:00

sc_logger.hh

misc: Adopt the gem5 namespace

2021-07-01 19:08:24 +00:00

sc_module.cc

misc: Adopt the gem5 namespace

2021-07-01 19:08:24 +00:00

sc_module.hh

misc: Adopt the gem5 namespace

2021-07-01 19:08:24 +00:00

stats.cc

misc: Adopt the gem5 namespace

2021-07-01 19:08:24 +00:00

stats.hh

util: Rename recently renamed namespaces

2021-06-07 00:11:42 +00:00

README

This directory contains a demo of C++ configuration of gem5.  The intention
is to provide a mechanism to allow pre-generated config.ini files generated
by Python-based gem5 to be reloaded in library-base versions of gem5
embedded in other systems using C++ calls for simulation control.

This directory contain a demo of hosting a C++ configured version of gem5
onto SystemC's event loop.  The hosting is achieved by replacing 'simulate'
with a SystemC object which implements an event loop using SystemC scheduler
mechanisms.

The sc_... files here should probably be hosted in a diferent directory and
buildable as a library.

Files:

    main.cc                 -- demonstration top level
    sc_logger.{cc,hh}       -- rehosting of DPRINTF onto SC_REPORT
    sc_module.{cc,hh}       -- SystemC simulation loop base class
    sc_gem5_control.{cc,hh} -- Alternative extra wrapping to allow gem5
                                Systems to be instantiated as single
                                sc_module objects.
    stats.{cc,hh}           -- Stats dumping (copied from util/cxx_config)

Read main.cc for more details of the implementation and sc_... files for

To build:

First build gem5 as a library with cxx-config support and (optionally)
without python.  When building the library, disable gem5's native SystemC
API support, as that will conflict with the external version.  Also build a
normal gem5 (cxx-config not needed, Python needed):

> cd ../../..
> scons build/ARM/gem5.opt
> scons --with-cxx-config --without-python USE_SYSTEMC=0 \
>       build/ARM/libgem5_opt.so
> cd util/systemc

Note: For MAC / OSX this command should be used:
> scons --with-cxx-config --without-python USE_SYSTEMC=0 \
>       build/ARM/libgem5_opt.dylib

Set a proper LD_LIBRARY_PATH e.g. for bash:
> export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/path/to/gem5/build/ARM/"

or for MAC / OSX:
> export DYLD_LIBRARY_PATH="$DYLD_LIBRARY_PATH:/path/to/gem5/build/ARM/"


Then edit the Makefile to set the paths for SystemC, e.g:

    Linux:
    SYSTEMC_INC = /opt/systemc/include
    SYSTEMC_LIB = /opt/systemc/lib-linux64

    MAC / OSX:
    SYSTEMC_INC = /opt/systemc/include
    SYSTEMC_LIB = /opt/systemc/lib-macosx64

Then run make:

> make

Make a config file for the C++-configured gem5 using normal gem5

> ../../../build/ARM/gem5.opt ../../../configs/example/se.py -c \
>       ../../../tests/test-progs/hello/bin/arm/linux/hello

The binary 'gem5.opt.cxx' can now be used to load in the generated config
file from the previous normal gem5 run.

Try:

> ./gem5.opt.cxx m5out/config.ini

This should print:

> Hello world!

The .ini file can also be read by the Python .ini file reader example:

> ../../../build/ARM/gem5.opt ../../../configs/example/read_ini.py \
>       m5out/config.ini

If you are interested in SystemC Transaction Level Modeling (TLM2) please have
a look into /util/tlm.