A data profiler maintains one counter for every interval of addresses that differ only in the last granularity bits. This is used for various profiling tasks, for example counting the number of cache misses in each of the intervals.
conf_object, log_object, data_profiler, address_profiler
- cell-change
- Notifier that is triggered after the object's cell was changed.
- object-delete
- Notifier that is triggered just before Simics object is deleted.
- queue-change
- Notifier that is triggered after the object's clock was changed. New clock can be obtained with the SIM_object_clock function.
-
clear
– clear data profiler
-
physical_addresses
-
Pseudo attribute;
read/write access; type:
i
True if the profiler uses physical addresses, false if it uses virtual addresses.
-
description
-
Pseudo attribute;
read/write access; type:
s
Description of what data the profiler represents
-
counter
-
Pseudo attribute;
read/write access; type:
Unknown
Access the counter at an address.
-
granularity
-
Pseudo attribute;
read/write access; type:
i
Granularity of the profiler, in address bits.
-
data
-
Pseudo attribute;
read-only access; type:
[[ii]*]
list of (address, counter) pairs
Simics Core