spolstra / HotSniper

An EDA toolchain for interval thermal simulations of 2D multi-/many-cores in an open system.
Other
1 stars 0 forks source link

Mismatch powertrace component names and floorplan names #1

Closed spolstra closed 4 months ago

spolstra commented 4 months ago

Powertrace has C_0_CALU and C_0_IALU while floorplan used the C_0_cALU and C_0_iALU. The same is true for the other cores.

spolstra commented 4 months ago

Fixing the names in the floorplans and core templates makes the most sense here.

spolstra commented 4 months ago

Investigate why this mismatch did not trigger any issues in hotspot. How did it manage to calculate the temperatures if the sub component names did not match the floorplan.

spolstra commented 4 months ago

The matching of the component names in the power trace with the component names in the floorplan is case insensitive. flp.c uses strcasecmp() to check the names. Checked by running hotspot manually:

novo[74]:~/projects/HotSniper/benchmarks/backup [tsp]$ ../../hotspot/hotspot -c /home/spolstra/projects/HotSniper/hotspot/gainestown_4_core_l3_cache.hotspot_config -f /home/spolstra/projects/HotSniper/hotspot/gainestown_4_core_l3_cache.flp -sampling_intvl 0.001 -p /home/spolstra/projects/HotSniper/benchmarks/backup/InstantaneousPower.log -o /home/spolstra/projects/HotSniper/benchmarks/backup/InstantaneousTemperature.log

Changing the case did give an error, but changing the name itself triggered the error such as:

error: block C_0_jALU not found