Andreas Sandberg 60b26f1546 base: Refactor logging to make log level selection cleaner ... It's currently possible to change the log level in gem5 by tweaking a set of global variables. These variables are currently exposed to Python using SWIG. This mechanism is far from ideal for two reasons: First, changing the log level requires that the Python world enables or disables individual levels. Ideally, this should be a single call where a log level is selected. Second, exporting global variables is poorly supported by most Python frameworks. SWIG puts variables in their own namespace and PyBind doesn't seem to support it at all. This changeset refactors the logging code to create a more abstract interface. Each log level is associated with an instance of a Logger class. This class contains common functionality, an enable flag, and a verbose flag. Available LogLevels are described by the LogLevel class. Lower log levels are used for more critical messages (PANIC being level 0) and higher levels for less critical messages. The highest log level that is printed is controlled by calling Logger:setLevel(). Change-Id: I31e44299d242d953197a8e62679250c91d6ef776 Signed-off-by: Andreas Sandberg <andreas.sandberg@arm.com> Reviewed-by: Gabor Dozsa <gabor.dozsa@arm.com> Reviewed-by: Curtis Dunham <curtis.dunham@arm.com> Reviewed-by: Jason Lowe-Power <jason@lowepower.com>		2017-02-27 11:25:01 +00:00
..
_m5	python: Move native wrappers to the _m5 namespace	2017-01-27 12:40:01 +00:00
m5	python: Add a generalized mechanism to configure stats	2017-02-27 11:24:59 +00:00
swig	base: Refactor logging to make log level selection cleaner	2017-02-27 11:25:01 +00:00
importer.py	base: Make the Python module loader PEP302 compliant	2013-06-03 13:51:03 +02:00
SConscript	python: Move native wrappers to the _m5 namespace	2017-01-27 12:40:01 +00:00