[gem5-users] l3 cache

Does the standard system call script (se.py) model an L3 cache or is it only L1 and L2? When I ran it with the -h option, I saw an option for L3 caches so I used that: build/ARM/gem5.opt configs/example/se.py --caches --l2cache --num-dirs=1 --num-l2caches=1 --num-l2caches=1 --l1d_size=16kB

Re: [gem5-users] l3 cache

Hello, L3 cache is not implemented in gem5 but you can manually implement it (and add a command line option such as --l3caches), unless you are using ruby (as far as I know due to not having a 3-level coherence protocol). You may want to check this tutorial for more information about adding

Re: [gem5-users] Ubuntu, booted on gem5, is not syncing the file-system?

Jason, I changed it RAW disk image following http://www.gem5.org/BBench-gem5. After that I see some files are reflected on the disk image. However, not all are seen on the mounted disk image. Earlier I had the COW disk image and there I didn’t see any of the files being written to the disk

Re: [gem5-users] flit size and int_link width in garnet2

On Feb 27, 2017, at 3:32 PM, raziye deylamsalehi > wrote: Hi Tushar as I see in mailing list and documentation the num_dir is equal with number of memory controllers. That is correct? As far as I know, in most coherence

Re: [gem5-users] Ubuntu, booted on gem5, is not syncing the file-system?

Hi Somnath, By default the disk image is created as a "COW" or copy-on-write image. Thus, all changes made to the disk are made to an new copy that is deleted when gem5 exits. If you want your changes to be permanent you need to modify the way the disk image is created and use a raw disk image,

Re: [gem5-users] l3 cache

A more up-to-date version of the tutorial can be found at http://learning.gem5.org. This is where it will live for the foreseeable future. Jason On Mon, Feb 27, 2017 at 5:58 AM Serhat Gesoglu < serhat.geso...@manchester.ac.uk> wrote: > Hello, > L3 cache is not implemented in gem5 but you can

Re: [gem5-users] gem5 segmentation fault with SPEC CPU2006 benchmarks

Hi Muzamil, Have you tried running gdb to find where the segfault is occurring. That's where I would start. Using some debug flags would be helpful too after you narrow down the problem. Cheers, Jason On Wed, Feb 22, 2017 at 6:31 PM Muzamil Rafique wrote: > Hi

Re: [gem5-users] Linux booting problem in ARM NOC

Hi Sharjeel, It's clear that Ruby+ARM currently doesn't work. It's going to take some effort and some code changes in Ruby to get it to work correctly. It's good that a single core boots. You should try something *very simple* with 2 cores. For instance, use MI_example and the Pt2Pt topology with