Hello,
My guess is that it may not be possible, because gprof uses the OS
interruptions to profile your code. Given that in the SE mode,
syscalls are emulated by the host
(http://en.wikipedia.org/wiki/Gprof), even if it works the results
would be wrong.
Regards,
2015-02-12 19:20 GMT+01:00, Raul
Hello,
Not sure if this is your problem, but If the crash comes from
misaligned loads, you can try to align you data structures with
compiler directives (e.g., #pragma in C or __attribute__ in gcc).
You can also try gdb to check where in the code it happens (yes,
inside the FS mode).
Regards,
2
Hello,
You can check:
1) How many cores there are in the config.ini (or equivalent) file
2) How many cores the kernel detects during boot time (system.terminal
file: [0.060288] Brought up 2 CPUs)
Regards,
2015-01-31 10:53 GMT+01:00, Tayebe Sadeghi via gem5-users :
> HiExcuse me,i have a pro
Hello,
To my understanding, number_cache_levels reflects what you said in
number 1. In number 2, I personally only tried number_of_L2s=1.
When you mention that no power difference was observed with and
without L2 cache, did you see the L2 cache in the McPAT output file?
If you don't have detailed
Hello,
I saw similar problems in the mailing list archive, the better is to always
check the config.ini. If this is a bug or not, I agree with you that the
parameters by default should not be set in Options.py
Regards,
--
Fernando A. Endo, PhD student and researcher
Université de Grenoble, UJ
Hello,
If the core configuration is multi-issue, that can happen. You can check
the issueWidth in the config.ini file, for example.
Regards,
--
Fernando A. Endo, PhD student and researcher
Université de Grenoble, UJF
France
2014-05-26 16:08 GMT+02:00 Anderson Sartor via gem5-users <
gem5-use
Hello,
To my understanding, wbDepth represents a kind of "average and
effective execution stage depth": wbWidth*wbDepth represents the
maximum allowed in-flight instructions in the EXE, i.e. instructions
that issued but did not writeback yet.
Given that, I agree that such buffers would be better
Hello,
One just need to put the first bench in the background, isn't it?
Regards,
2014-05-09 18:12 GMT+02:00, Seyedhamidreza Motaman via gem5-users
:
> Hello All,
>
> Is it possible to run two benchmarks of parsec suite concurrently in FS
> mode??
>
> Regards,
> Hamid
>
--
--
Fernando A. Endo
Hello,
The message "kernel too old" usually appears when the toolchain you're
using embed linux headers newer than the version of your kernel.
Are you using the native gcc in the gem5's disk image (the new one)? I
had no major problems to compile PARSEC 3.0. There were only a few
dependencies to
