[gem5-users] L1 dcache misses with full-system simulation

2018-06-03 Thread Choe, Jiwon
Hi,

I am running some multicore, multithreaded benchmarks (1 thread/core) on a
gem5 full-system simulation, and I am having trouble interpreting the data
cache misses that I am seeing.

As far as I am concerned, the threads do not share any data. However, I am
seeing an increase in data cache misses concentrated at a certain address
with more threads.
I looked into the packet requests that cause the cache misses, and the
virtual and phyisical address of the requests are the same. Because of
this, I am wildly guessing that the misses might be due to some OS
interaction, but I might be completely off.

This might be a long shot, but has anyone seen similar behavior with
multithreaded full-system simulations? I would really appreciate any advice
or help.

Thanks in advance,
Jiwon
___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Re: [gem5-users] execution problem hello.c in architecture armv8 big.LITTLE

2018-06-03 Thread Ciro Santilli
Sorry, those images are undocumented and I don't know how they are
generated + parsec is highly unmaintained and not made with cross
compilation in mind.

The best advice I can give at the moment is: use my setup:
https://github.com/cirosantilli/linux-kernel-module-cheat/tree/16de55dd2f89ae44c1ee0fee1c39d23ee2b36b13#parsec-benchmark
which I understand and have clearly documented what works and what
does not.

In the future I might try to understand the state of the current
images and contribute better ones / documentation.

On Sun, Jun 3, 2018 at 1:02 PM, commerce _com  wrote:
> hi ciro,
>
> is there is another solution to solve this problem please, because the
> execution of the kernel is normal, but the problem is that I think it does
> not know the comandes line as cd in the script.Rcs, and here is the problem
> I found:
> for the command "ls" it works normal
>
> here are the image disk files
>
> bin dev home lost + found mnt proc run srv tmp var
> boot etc lib media root opt sbin sys usr
>
> but for "cd root" it blocked
> / tmp / script: line 5: cd: root: No such file or directory
>
>
> thanks advance,
>
> com_.
>
> 2018-06-01 14:48 GMT+01:00 commerce _com :
>>
>> Hi Oscar,
>>
>> I tried this script and I think the same problem:
>> #! / Bin / bash
>> ls
>> cd / home /
>> ls
>> cd root
>> ls
>> cd parsec
>> ./Hello
>>
>> Here is the result obtained:
>> bin dev home lost + found mnt proc run srv tmp var
>> boot etc lib media root opt sbin sys usr
>> / tmp / script: line 5: cd: root: No such file or directory
>> / tmp / script: line 7: cd: parsec: No such file or directory
>> / tmp / script: line 8: ./hello: No such file or directory
>>
>> here is my system.terminal file
>>
>> thanks advance.
>>
>> com_.
>>
>> 2018-06-01 10:31 GMT+02:00 Oscar Rosell :
>>>
>>> Hi,
>>>
>>> The important line is this one:
>>>
>>> / tmp / script: line 3: cd: / home / root / parsec: No such file or
>>> directory
>>>
>>> No way you can get the binary running if you cannot cd to the directory
>>> where the binary is located. That has no relation with how the binary was
>>> compiled.
>>>
>>> My intuition is that the directory is in fact "/root/parsec". It's just a
>>> guess based on the absence of home directory for root user in my Ubuntu
>>> (although I don't know which image you're using). To be sure just add an ls
>>> to show the directory at each point like this:
>>>
>>> PARSEC_DIR = "/ home / root / parsec"
>>> ls
>>> cd /home/
>>> ls
>>> cd root
>>> ls
>>> cd parse
>>> ls
>>>
>>>
>>> On 01/06/18 08:45, Ciro Santilli wrote:

 This is not required, the best thing to do is to find what is the
 proper compatible cross compiler for the image:

 https://stackoverflow.com/questions/31929092/trying-to-run-a-cross-compiled-executable-on-target-device-fails-with-no-such-f/49993116#49993116

 On Fri, Jun 1, 2018 at 6:34 AM, Tung Hoang 
 wrote:
>
> You may need “-static” for arm cross-compiling.
>
> /T
>
> On Thu, May 31, 2018 at 3:19 PM commerce _com
> 
> wrote:
>>
>> Hi ciro,
>>
>> I'm sure the binary of the compilation  is in the image on the path: /
>> home / root / parsec
>>
>> but I did not understand how to solve this problem; Please.
>>
>>
>> com_.
>>
>> 2018-05-31 23:02 GMT+02:00 Ciro Santilli :
>>>
>>> Likely incompatible compiler using wrong dynamic loader, do "file
>>> hello", see "interpreter /some/path", and check if "/some/path" is
>>> present on guest.
>>>
>>> On Thu, May 31, 2018 at 9:33 PM, commerce _com
>>> 
>>> wrote:

 Hi all,

 i need to run hello.c in an architecture armv8 big.LITTLE
 I compile hello_word.c by a crosscompiler here is the command:
 arm-linux-gnueabihf-gcc hello.c -o hello

 I added the binarie of the compilation to the linaro aarch64 image,
 with I
 generated this .rcs script as follows:
 #! / Bin / bash
 PARSEC_DIR = "/ home / root / parsec"
 cd $ PARSEC_DIR
 pwd
 ./Hello

 I typed the following command:

 sudo build / ARM / gem5.opt configs / example / arm /
 fs_bigLITTLE.py
 --kernel = / media / ali / ali / gem5-master / aarch-system-20180409
 /
 binaries / vmlinux.vexpress_gem5_v1_64 --dtb = / media / ali / ali /
 gem5-master / aarch-system-20180409 / binaries /
 armv8_gem5_v1_big_little_2_2.dtb --bootscript = / home / ali /
 desktop
 /
 rcs_file / parsec_rcs / hello.rcS - caches

 the execution of the kernel it works normal but when it passes the
 stage of
 execution of the hello I found this result:

 / tmp / script: line 3: cd: / home / root / parsec: No such file or
 directory
 /
 / tmp / script: line 5: ./hello: No such file or directory