Difference between revisions of "BBench"
From gem5
m (→Running BBench on Android with Gem5) |
m (→Running BBench on Android with gem5) |
||
| Line 16: | Line 16: | ||
# The default gem5 scripts look for a kernel called ''vmlinux.arm.smp.fb.2.6.38.8'' and a disk image called ''android-mbr.img''. You will have to either rename the files or create softlinks to them once you have downloaded and untarred them. | # The default gem5 scripts look for a kernel called ''vmlinux.arm.smp.fb.2.6.38.8'' and a disk image called ''android-mbr.img''. 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 ''typically path_to_gem5_root/configs/boot/''. | # The bbench.rcS file should be placed wherever you keep your rcS scripts. This is ''typically path_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: | + | #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')]'' |
| − | |||
'''Note: Android only runs on the ARM ISA.''' | '''Note: Android only runs on the ARM ISA.''' | ||
Revision as of 14:04, 10 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.
- Point the M5_PATH environment variable to this location. E.g, type export 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 type make in this directory and the bootloader will be compiled. Copy the resulting boot.arm file to the same directory where you kernel is located. E.g., path_to_gem5_system/system/binaries/
- The default gem5 scripts look for a kernel called vmlinux.arm.smp.fb.2.6.38.8 and a disk image called android-mbr.img. 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 typically path_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')]
Note: Android only runs 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.
