Hi Rabab,
You need to merge your gem5 command into the agenda. The gem5_binary, gem5_args
and gem5_vio_args are combined to create the overall command line which is used
to run gem5. In your case you want to do something similar to the following:
config:
device: gem5_android
device_config:
gem5_binary: "./build/ARM/gem5.opt"
gem5_args: "configs/example/fs.py
--kernel=/dist/m5/system/binaries/vmlinux-linaro
--disk-image=/dist/m5/system/disks/android-kitkat-my5-kitpakage-WA.img
--cpu-type=AtomicSimpleCPU --frame-capture -n 1 --caches --l2cache
--l1d_size=16kB --l1i_size=16kB --l2_assoc=16 --l2_size=2MB --mem-size=256MB
--mem-type=LPDDR3_1600_x32 --os-type=android-kitkat"
gem5_vio_args: "--workload-automation-vio={}"
temp_dir: "/tmp"
checkpoint: True
run_delay: 10
core_names: ['a15']
username: root
reboot_policy: never
result_processors: [~sqlite]
instrumentation: [~cpufreq]
workloads:
- id: dhrystone
workload_name: dhrystone
iterations: 1
This will run gem5 with your kernel and disk image. Workload Automation will
automatically create a directory in the temp_dir folder, and will remove it
again once the simulation completes. This directory will be mounted over VirtIO
into your simulated system and is used for transferring files into the
simulated system. Once the system has booted, the above agenda will create a
checkpoint in the gem5 directory under your WA output directory. This can be
used to skip booting the system for future experiments. Finally, WA will
transfer across some binaries, including Dhrystone, and will execute the
workload. Results will be transferred back to your system before terminating
the gem5 simulation automatically.
I hope that this makes sense. If not, let me know. Good luck!
Sascha
________________________________
From: gem5-users <[email protected]> on behalf of Alomairy R.M.
<[email protected]>
Sent: 01 August 2016 11:51:24
To: gem5 users mailing list
Subject: Re: [gem5-users] System stuck after adding VirtIO part of Workload
automation
Dear Sascha,
Thank you for respond.
This is my agenda
config:
device: gem5_android
device_config:
gem5_binary: "./build/ARM/gem5.opt"
gem5_args: "configs/example/fs.py"
gem5_vio_args: "--workload-automation-vio={}"
temp_dir: "/tmp"
checkpoint: True
run_delay: 10
core_names: ['a15']
username: root
reboot_policy: never
result_processors: [~sqlite]
instrumentation: [~cpufreq]
workloads:
- id: dhrystone
workload_name: dhrystone
iterations: 1
I am not sure how to run the image because in the agenda there is no parameter
for specifying the path to android image, so I make regular run using the
following command:
command line: ./build/ARM/gem5.opt configs/example/fs.py
--kernel=/dist/m5/system/binaries/vmlinux-linaro
--disk-image=/dist/m5/system/disks/android-kitkat-my5-kitpakage-WA.img
--cpu-type=AtomicSimpleCPU --frame-capture -n 1 --caches --l2cache
--l1d_size=16kB --l1i_size=16kB --l2_assoc=16 --l2_size=2MB --mem-size=256MB
--mem-type=LPDDR3_1600_x32 --os-type=android-kitkat
and I run the agenda in separate way.
Could you please advice me how to run the img in FS and how to run WA agenda?
because this part is not clear for me.
I really appreciate your help.
Thank you,
Rabab
________________________________________
From: gem5-users [[email protected]] on behalf of Sascha Bischoff
[[email protected]]
Sent: Monday, August 01, 2016 10:59 AM
To: gem5 users mailing list
Subject: Re: [gem5-users] System stuck after adding VirtIO part of
Workload automation
Hi Rabab,
Sorry that you are having issues.
Could you please send your Workload Automation agenda? I think that the issue
might lie with the temp_dir and gem5_vio_args parameters. It looks like the
--workload-automation-vio argument is not being passed to gem5, which is
generated through a combination of the two aforementioned parameters from your
WA agenda.
You agenda should have a gem5_vio_args entry and temp_dir entry similar to the
ones shown in the example agenda here:
http://gem5.org/WA-gem5#Using_gem5_with_Workload_Automation
Thanks,
Sascha
-----Original Message-----
From: gem5-users [mailto:[email protected]] On Behalf Of Alomairy R.M.
Sent: 30 July 2016 13:05
To: [email protected]
Subject: [gem5-users] System stuck after adding VirtIO part of Workload
automation
Hello all,
System stuck after adding VirtIO part of Workload automation
I followed the instructions of Workload Automation.
1-I installed diod and
2-I used the following:
patch -p1 << EOF
I added here the VirtIO device to the default full-system simulation script
EOF
3- I added the following to vexpress_gem5_defconfig when building the image:
CONFIG_NET_9P=y
CONFIG_NET_9P_VIRTIO=y
CONFIG_9P_FS=y
CONFIG_9P_FS_POSIX_ACL=y
CONFIG_9P_FS_SECURITY=y
CONFIG_VIRTIO_BLK=y
4- I followed the steps to install pip and wa in the workload automation
website.
5- I tried different ----machine-type, RealView_PBX or VExpress_GEM5_V1 with
armv7_gem5_v1_1cpu.dtb.
I got the following errors, I and the system stuck and does not proceed:
command line: ./build/ARM/gem5.opt configs/example/fs.py
--kernel=/dist/m5/system/binaries/vmlinux-linaro
--disk-image=/dist/m5/system/disks/android-kitkat-my5-kitpakage-WA.img
--cpu-type=AtomicSimpleCPU --frame-capture -n 1 --caches --l2cache
--l1d_size=16kB --l1i_size=16kB --l2_assoc=16 --l2_size=2MB --mem-size=256MB
--mem-type=LPDDR3_1600_x32 --os-type=android-kitkat
Global frequency set at 1000000000000 ticks per second
warn: DRAM device capacity (512 Mbytes) does not match the address range
assigned (256 Mbytes)
info: kernel located at: /dist/m5/system/binaries/vmlinux-linaro
Listening for system connection on port 5900
Listening for system connection on port 3456
0: system.remote_gdb.listener: listening for remote gdb #0 on port 7000
warn: ClockedObject: More than one power state change request encountered
within the same simulation tick
info: Using bootloader at address 0x10
info: Using kernel entry physical address at 0x80008000
info: Loading DTB file:
/dist/m5/system/binaries/vexpress.aarch32.ll_20131205.0-gem5.1cpu.dtb at
address 0x88000000
**** REAL SIMULATION ****
warn: Existing EnergyCtrl, but no enabled DVFSHandler found.
info: Entering event queue @ 0. Starting simulation...
warn: Not doing anything for miscreg ACTLR
warn: Not doing anything for write of miscreg ACTLR
warn: The clidr register always reports 0 caches.
warn: clidr LoUIS field of 0b001 to match current ARM implementations.
warn: The csselr register isn't implemented.
diod: exports should begin with '/'
--------------------------------------------------
telnet localhost 3456
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Moreover, I also tried to run the existing Ubuntu ARM img, the FS stuck with
the same error.
I think there is something error with adding VirtIO device.
Is there any missing step or any mistake?
Could you please help me to solve this issue?
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended recipient,
please notify the sender immediately and do not disclose the contents to any
other person, use it for any purpose, or store or copy the information in any
medium. Thank you.
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended recipient,
please notify the sender immediately and do not disclose the contents to any
other person, use it for any purpose, or store or copy the information in any
medium. Thank you.
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
