Hi Zhantong,
I read the documentation page for pinball2elf that you just referred, but I
don't quite understand how to get the 4 values used at the beginning of the
example ("-control start:address:0x000814187:count84738:global -control
stop:address:0x0009decb1:count34069:global"). And should I use the whole
program or region pinball to pass into the command? What are the meanings of
the output?
Right now, I'm using the pinpoints.py script downloaded from Intel to generate
region pinballs, and there's no involvement of SniperSim in my toolchain. Could
my setup be wrong? I recall Prof. Lowe-Power said in a recent thread that GEM5
currently only supports ELFies generated by the Sniper simulator.
Fangjia
________________________________
From: Zhantong Qiu via gem5-users <[email protected]>
Sent: Thursday, April 6, 2023 2:21
To: [email protected] <[email protected]>
Cc: Zhantong Qiu <[email protected]>
Subject: [gem5-users] Simulating ELFies in GEM5
---- External Email: Use caution with attachments, links, or sharing data ----
Hi Fangjia,
The crash might be due to the ELFie trying to access pages that are not
recorded because the ELFie execution is unconstrained. Therefore, we need to
know where to end the simulation to avoid a possible crash.
The PC count pairs are the markers for the gem5 simulator to know where the
right ROI starts and ends for the ELFie execution. I believe ELFie can generate
information about the starting and ending PC count pair for
simulation(https://github.com/intel/pinball2elf#example-of-account-in-warmup
simulation-specification<https://github.com/intel/pinball2elf#example-of-pccount-in-warmupsimulation-specification>).
With the SIMPOINT_BEGIN events, the simulation will exit into the Python
script and allow us to specify what to do for the events. In this case, we can
start at the right beginning and exit the simulation at the right ending of the
ROI.
Best,
Zhantong
_______________________________________________
gem5-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
