Difference between revisions of "BBench-gem5"
From gem5
(→Running BBench on Android with gem5) |
(→Running BBench on Android with gem5) |
||
| Line 10: | Line 10: | ||
# Create a directory where you will place your gem5 full-system files, call this directory ''system''. Inside this directory create two separate directories, one called ''binaries'' and the other called ''disks''. This can be the same directories you already have gem5 full-system files that you downloaded from the [[Download]] page. | # Create a directory where you will place your gem5 full-system files, call this directory ''system''. Inside this directory create two separate directories, one called ''binaries'' and the other called ''disks''. This can be the same directories you already have gem5 full-system files that you downloaded from the [[Download]] page. | ||
| − | # Point the | + | # Point the <code>M5_PATH</code> environment variable to this location. E.g, type <code>export M5_PATH=path_to_gem5_system/system/</code> |
| − | # Place the kernel in the | + | # Place the kernel in the <code>path_to_gem5_system/system/binaries/</code> directory |
| − | # Place the disk image in the | + | # Place the disk image in the <code>path_to_gem5_system/system/disks/</code> directory |
| − | # Build the ARM bootloader and place it in the same directory as the kernel. The code for the bootloader is typically in | + | # Build the ARM bootloader and place it in the same directory as the kernel. The code for the bootloader is typically in <code>path_to_gem5_root/system/arm/simple_bootloader/</code>. Simply type <code>make</code> in this directory and the bootloader will be compiled. Copy the resulting <code>boot.arm</code> file to the same directory where you kernel is located. E.g., <code>path_to_gem5_system/system/binaries/</code>. Note this is also available within the ARM Full system files on the [[Download]] page. |
| − | # The default gem5 scripts look for a kernel called | + | # The default gem5 scripts look for a kernel called <code>vmlinux.arm.smp.fb.2.6.38.8</code> and a disk image called <code>android-mbr.img</code>. You will have to either rename the files or create softlinks to them once you have downloaded and untarred them. |
| − | # The bbench.rcS file should be placed wherever you keep your rcS scripts. This is | + | # The <code>bbench.rcS</code> file should be placed wherever you keep your rcS scripts. This is typically <code>path_to_gem5_root/configs/boot/</code>. |
| − | #You will also need to modify your Benchmarks.py file to include bbench, i.e., include a line like the following: | + | # You will also need to modify your Benchmarks.py file to include bbench, i.e., include a line like the following: <code>'bbench': [SysConfig('bbench.rcS', '256', 'android-mbr.img')]</code> |
| − | # Assuming you have followed the steps above, and built a full-system version of gem5 for ARM, you should be able to type | + | # Assuming you have followed the steps above, and built a full-system version of gem5 for ARM, you should be able to type <code>/path_to_gem5_root/build/ARM_FS/m5.fast configs/example/fs.py -b bbench</code> to run Android on ARM. |
| − | '''Note: Android | + | '''Note: These instructions and images are only for Android on the ARM ISA.''' |
== Android Full-System Files == | == Android Full-System Files == | ||
Revision as of 02:03, 11 November 2011
This page is under heavy construction
Contents
Source
A tarball of the BBench source can be found here:
Running BBench on Android with gem5
Everything required to run BBench on gem5 is provided in the next section. You will need the kernel, the disk image (containing BBench), and the rcS script.
- Create a directory where you will place your gem5 full-system files, call this directory system. Inside this directory create two separate directories, one called binaries and the other called disks. This can be the same directories you already have gem5 full-system files that you downloaded from the Download page.
- Point the
M5_PATHenvironment variable to this location. E.g, typeexport M5_PATH=path_to_gem5_system/system/ - Place the kernel in the
path_to_gem5_system/system/binaries/directory - Place the disk image in the
path_to_gem5_system/system/disks/directory - Build the ARM bootloader and place it in the same directory as the kernel. The code for the bootloader is typically in
path_to_gem5_root/system/arm/simple_bootloader/. Simply typemakein this directory and the bootloader will be compiled. Copy the resultingboot.armfile to the same directory where you kernel is located. E.g.,path_to_gem5_system/system/binaries/. Note this is also available within the ARM Full system files on the Download page. - The default gem5 scripts look for a kernel called
vmlinux.arm.smp.fb.2.6.38.8and a disk image calledandroid-mbr.img. You will have to either rename the files or create softlinks to them once you have downloaded and untarred them. - The
bbench.rcSfile should be placed wherever you keep your rcS scripts. This is typicallypath_to_gem5_root/configs/boot/. - You will also need to modify your Benchmarks.py file to include bbench, i.e., include a line like the following:
'bbench': [SysConfig('bbench.rcS', '256', 'android-mbr.img')] - Assuming you have followed the steps above, and built a full-system version of gem5 for ARM, you should be able to type
/path_to_gem5_root/build/ARM_FS/m5.fast configs/example/fs.py -b bbenchto run Android on ARM.
Note: These instructions and images are only for Android on the ARM ISA.
Android Full-System Files
These files contain everything you need to get Android, and BBench, up and running on gem5.
- Kernel -- Pre-compiled Android kernel and config file.
- Disk Image -- Disk image with a pre-compiled Android Gingerbread file system. This disk image contains all of the files generated during initial boot, as well as a self-terminating version of BBench and BusyBox.
- Clean Disk Image -- Disk image containing only the pre-compiled Android Gingerbread file system. This disk image contains no benchmarks and has never been booted.
- rcS Script -- Script for automating a BBench run on gem5.
Building Your Own Android File System and Kernel
Coming Soon!
Other Benchmarks
Coming soon!
Publications
If you use BBench or any of our benchmarks in your work please cite our IISWC 2011 paper:
A. Gutierrez, R.G. Dreslinski, T.F. Wenisch, T. Mudge, A. Saidi, C. Emmons, and N. Paver. Full-System Analysis and Characterization of Interactive Smartphone Applications. IEEE International Symposium on Workload Characterization, Austin, TX, November 2011.
