Hello, When I enable stride prefetcher on L1 dcache, and run timing mode on 4 cores configuration, The stats.txt shows that only one core (core1) has prefetch statistics.The number are zero on other core's prefetcher. system.cpu1.dcache.prefetcher.prefetcher.num_hwpf_identified 10455 # number of hwpf identified system.cpu1.dcache.prefetcher.prefetcher.num_hwpf_already_in_mshr 0 # number of hwpf that were already in mshr system.cpu1.dcache.prefetcher.prefetcher.num_hwpf_already_in_cache 358 # number of hwpf that were already in the cache system.cpu1.dcache.prefetcher.prefetcher.num_hwpf_already_in_prefetcher 0 # number of hwpf that were already in the prefetch queue system.cpu1.dcache.prefetcher.prefetcher.num_hwpf_evicted 0 # number of hwpf removed due to no buffer left system.cpu1.dcache.prefetcher.prefetcher.num_hwpf_removed_MSHR_hit 0 # number of hwpf removed because MSHR allocated system.cpu1.dcache.prefetcher.prefetcher.num_hwpf_issued 10097 # number of hwpf issued system.cpu1.dcache.prefetcher.prefetcher.num_hwpf_span_page 154 # number of hwpf spanning a virtual page system.cpu1.dcache.prefetcher.prefetcher.num_hwpf_squashed_from_miss 0 # number of hwpf that got squashed due to a miss aborting calculation time The behavior just likes only core1 enables the prefetcher. What is the reason of the problem? Thanks! My command are: First time: ./build/X86/m5.fast ./configs/example/fs.py --cpu-type=atomic -n4 --script=/Barnes_core4 and will create a checkpoint file before ROI part. Second time: ./build/X86/m5.fast ./configs/example/fs.py --cpu-type=timing -n4 --caches --l2cache -r1 restore from checkpoint, and run simulation on timing mode.

So, you don't have system.cpu0.dcache.prefetcher ? On 11/8/12, IC <romekevin(a)yahoo.com.tw> wrote: > Hello, > > When I enable stride prefetcher on L1 dcache, and run timing mode on 4 > cores configuration, > > The stats.txt shows that only one core (core1) has prefetch statistics.The > number are zero on other core's prefetcher. > > system.cpu1.dcache.prefetcher.prefetcher.num_hwpf_identified > 10455 # number of hwpf identified > system.cpu1.dcache.prefetcher.prefetcher.num_hwpf_already_in_mshr > 0 # number of hwpf that were already in mshr > system.cpu1.dcache.prefetcher.prefetcher.num_hwpf_already_in_cache > 358 # number of hwpf that were already in the cache > system.cpu1.dcache.prefetcher.prefetcher.num_hwpf_already_in_prefetcher > 0 # number of hwpf that were already in the prefetch > queue > system.cpu1.dcache.prefetcher.prefetcher.num_hwpf_evicted > 0 # number of hwpf removed due to no > buffer left > system.cpu1.dcache.prefetcher.prefetcher.num_hwpf_removed_MSHR_hit > 0 # number of hwpf removed because MSHR > allocated > system.cpu1.dcache.prefetcher.prefetcher.num_hwpf_issued > 10097 # number of hwpf issued > system.cpu1.dcache.prefetcher.prefetcher.num_hwpf_span_page > 154 # number of hwpf spanning a virtual page > system.cpu1.dcache.prefetcher.prefetcher.num_hwpf_squashed_from_miss > 0 # number of hwpf that got squashed due to a miss > aborting calculation time > > The behavior just likes only core1 enables the prefetcher. > > What is the reason of the problem? > > Thanks! > > My command are: > First time: > ./build/X86/m5.fast ./configs/example/fs.py --cpu-type=atomic > -n4 --script=/Barnes_core4 > and will create a checkpoint file before ROI part. > > Second time: > ./build/X86/m5.fast ./configs/example/fs.py --cpu-type=timing > -n4 --caches --l2cache -r1 > restore from checkpoint, and run simulation on timing mode. > -- Regards, Mahmood