[gem5-users] Re: Lock implementation in Ruby Cache Memory and Request Queue

Hi, For 1, I meant automatically: “lines will not get blocked automatically”. As for 2, peek does not block anything unless you use the block_on mechanism. You can peek as many queues as you want as well as dequeue and enqueue as many as you want. Regards, Gabriel

[gem5-users] Re: Help needed regarding EL2 MSR MRS instruction call (Arm-v8a aarch64) in gem5

Hi Atul, Just to clarify your setup: Are you compiling your benchmark for Linux and running Linux + benchmark on gem5? Or are you running it baremetal on the simulated platform? There’s nothing inherently wrong on observing SVCs and MSR/MRS if your application contains some syscalls… If you re

[gem5-users] Help needed regarding EL2 MSR MRS instruction call (Arm-v8a aarch64) in gem5

Hello, I am running a benchmark binary compiled with clang with armv8a+fp+simd+crypto options. All the workloads of this compiled benchmark have similar performance in gem5 compared to actual mobile device except this one workload (quite simple workload, running Convolutional Neural Network by

[gem5-users] Re: Lock implementation in Ruby Cache Memory and Request Queue

Hi Gabriel, Thanks a lot for your reply. Here are some questions I have no answer: 1. In your email, you said "lines will not get blocked manually", does this mean a line will be blocked automatically when a state transition is happening? 2. As I know, peek mechanism will block the que