Could not establish SIFT connection while using benchmark

232 views
Skip to first unread message

imZoet

unread,
Dec 1, 2021, 5:58:36 AM12/1/21
to Sniper simulator
I use command: /run-sniper --benchmarks=splash2-fft-test-4 -c gainestown

but raised error. Here is the full record of my issue: 

zoet@zoet-VirtualBox:~/sniper/benchmarks$ ./run-sniper --benchmarks=splash2-fft-test-4 -c gainestown
[app0] [SPLASH] Benchmarks to run: fft
[app0] 
[app0] [SPLASH] [========== Running benchmark fft ==========]
[app0] [SPLASH] Setting up run directory: /tmp/tmpkau98y
[app0] [SPLASH] Running '/home/zoet/sniper/record-trace --routine-tracing -o /tmp/tmpKhdzgv/run_benchmarks -e 1 -r 1 -s 0 --roi -- /home/zoet/sniper/benchmarks/splash2/splash2/codes/kernels/fft/FFT -m10 -p4':
[app0] [SPLASH] [---------- Beginning of output ----------]
[SNIPER] Warning: Unable to use physical addresses for shared memory simulation.
[SNIPER] Start
[SNIPER] --------------------------------------------------------------------------------
[SNIPER] Sniper using SIFT/trace-driven frontend
[SNIPER] Running full application in DETAILED mode
[SNIPER] --------------------------------------------------------------------------------

[SNIPER] Enabling performance models
[SNIPER] Setting instrumentation mode to DETAILED
[RECORD-TRACE] Using the Pin frontend (sift/recorder)
E: Missing application name
Pin: pin-3.7-97619-0d0c92f4f
Copyright (c) 2003-2018, Intel Corporation. All rights reserved.

Usage: pin [OPTION] [-t <tool> [<toolargs>]] -- <command line>
Use -help for a description of options
[SNIPER] WARNING: No SIFT connections made yet. Waiting...
[SNIPER] ERROR: Could not establish SIFT connection, aborting! Check benchmark-app*.log for errors.
[SNIPER] End
[SNIPER] Elapsed time: 60.61 seconds

宋毓韬

unread,
Oct 25, 2022, 11:07:57 AM10/25/22
to Sniper simulator

I have the same question with you,  have you figure out this problem ?

Trevor E. Carlson

unread,
Oct 25, 2022, 9:14:43 PM10/25/22
to snip...@googlegroups.com, iam...@gmail.com, songyu...@gmail.com
Hello,

It looks like the --benchmarks run command line option might need to be fixed. Note that using that benchmarks option allows you to specify the number of threads that the application can run irrespective of the number of cores or threads in the hardware. This means that you’ll still need to specify the number of cores using the -n option. Below is the output of a work-around that should get you started for now (./run-sniper -p splash2-fft -i test -n 4 -c gainestown).

You can see what is happening in the error case by looking at the verbose output (adding the -v option). In this case, there seems to be two copies of Pin running, which looks like a run-sniper or record-trace issue. If you could open a GitHub issue on the problem [1], that would be great.

Trevor




[root@4cbec7b58193 benchmarks]# ./run-sniper -p splash2-fft -i test -n 4 -c gainestown

[SPLASH] Benchmarks to run: fft

[SPLASH] [========== Running benchmark fft ==========]
[SPLASH] Setting up run directory: /tmp/tmpZaN8vr
[SPLASH] Running 'SNIPER_APP_LD_PRELOAD=$LD_PRELOAD; unset LD_PRELOAD; /root/sniper/run-sniper -n 4 -m 'localhost' -d '/root/benchmarks' -c gainestown --roi --curdir=/root/benchmarks  --  /root/benchmarks/splash2/splash2/codes/kernels/fft/FFT -m10 -p4':

[SPLASH] [---------- Beginning of output ----------]
[SNIPER] Warning: Unable to use physical addresses for shared memory simulation.
[SNIPER] Start
[SNIPER] --------------------------------------------------------------------------------
[SNIPER] Sniper using SIFT/trace-driven frontend
[SNIPER] Running pre-ROI region in  CACHE_ONLY mode
[SNIPER] Running application ROI in DETAILED mode
[SNIPER] Running post-ROI region in FAST_FORWARD mode
[SNIPER] --------------------------------------------------------------------------------

[RECORD-TRACE] Using the Pin frontend (sift/recorder)

FFT with Blocking Transpose
   1024 Complex Doubles
   4 Processors
   65536 Cache lines
   16 Byte line size
   4096 Bytes per page

[HOOKS] Entering ROI

[SNIPER] Enabling performance models
[SNIPER] Setting instrumentation mode to DETAILED
[TRACE:1] -- DONE --
[TRACE:2] -- DONE --
[TRACE:3] -- DONE --
[SNIPER] Disabling performance models
[SNIPER] Leaving ROI after 1.50 seconds
[SNIPER] Simulated 0.4M instructions, 0.9M cycles, 0.39 IPC
[SNIPER] Simulation speed 243.2 KIPS (60.8 KIPS / target core - 16449.8ns/instr)
[SNIPER] Sampling: executed 10.94% of simulated time in detailed mode
[SNIPER] Setting instrumentation mode to FAST_FORWARD
[TRACE:0] -- DONE --
[HOOKS] Leaving ROI

                 PROCESS STATISTICS
            Computation      Transpose     Transpose
 Proc          Time            Time        Fraction
    0                36              3       0.08333

                 TIMING INFORMATION
Start time                        :      -1844408258
Initialization finish time        :      -1844408008
Overall finish time               :      -1844407972
Total time with initialization    :              286
Total time without initialization :               36
Overall transpose time            :                3
Overall transpose fraction        :          0.08333

[SNIPER] End
[SNIPER] Elapsed time: 4.82 seconds
[SPLASH] [----------    End of output    ----------]
[SPLASH] Done.



--
--
--
You received this message because you are subscribed to the Google
Groups "Sniper simulator" group.
To post to this group, send email to snip...@googlegroups.com
To unsubscribe from this group, send email to
snipersim+...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/snipersim?hl=en

---
You received this message because you are subscribed to the Google Groups "Sniper simulator" group.
To unsubscribe from this group and stop receiving emails from it, send an email to snipersim+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/snipersim/07636b3b-3d38-4b62-9424-ba3ec36984afn%40googlegroups.com.

Reply all
Reply to author
Forward
0 new messages