These changes are a step forward in the direction of the PEP8 style guide for
python code. They do not affect functionality itself.
See also:
https://www.python.org/dev/peps/pep-0008/
Created classes to get easily memory specifications and memory configurations.
Each class handles the peculiarities of the related XML file.
Other changes:
- git ignore file updated.
Other improvements:
- Added option to save changes to databases (e.g., save comments).
- When a database file changes on disk (overwritten by a rerun of DRAMSys or
changed by any external agent) the action save changes to DB is disabled,
since it is not safe anymore.
- Implemented menu options coherence. All actions except for "Open" (reload,
close, save, test and metrics) remain disabled until some database file is
open.
- Created a shortcut to close all: CTRL+Q
- Status messages containing a timestamp are displayed in the lower left
corner of the traceAnalyzer window when:
- User reloads the databases.
- User saves changes to the databases.
- Any of the open database files has changed on disk.
The number of bits reserved to describe the channel within the address
determines the maximum number of memory channels allowed.
The program will be aborted if the number of memory channels in the
configuration exceeds the maximum number of memory channels supported based on
the number of bits reserved in the address mapping configuration file.
Summary:
- The code was simplified
- Using a deque instead of a vector to implement the FIFO.
- Fixed a bug related to the removal of requests (payloads) from the FIFO. It
was possible that old requests were not properly removed and then processed
again after the memory manager had free()d the payload (and its extensions)
generating a segmentation fault.
Matthias sent me these scripts by e-mail.
This first commit adds them as they are (without any change).
In the future we can use them to create a video based on the temperature maps generated by DRAMSys.
Check if the provided temperature and retention time are in a valid range that
is covered by the input data stored in the errorMap. In case values are out of
range the maximum values provided are used and debug messages are generated to
alert the user.
