Kernel Performance Testing on ARM

By -
This post will be talking about , how you can do kernel regression , stress and performance testing on ARM architecture.

Setup:

To set up your ARM device , you need an image to get started. I was intending to test the latest compose(Fedora 26 1.4 Beta on Raspberry Pi 3 Model B). Download the file (Workstation raw-xz for armhfp) or any variant that you want to test.

Once the file is download, all you need to do is to get a SD card and write the img in the card.

There are two ways of doing it using "Fedora Media Writer" which can now burn the image for ARM devices. The other way is the old dd , here is how you do it using dd





Once the dd has executed itself successfully , its time to plug in the SD in ARM device and boot it up. Once the ARM device is booted up all you need to do is to
clone the kernel test suite from here


Dependencies and Execution:

You will need 2 packages
1.gcc
2.fedora-python

You can install them by executing "sudo dnf install fedora-python gcc"

Executing test cases:

Each test should be contained in a unique directory within the appropriate top level. The directory must contain an executable 'runtest.sh' which will drive the specific test. There is no guarantee on the order of execution. Each test should be fully independent, and have no dependency on other tests. The top level directories are reflective of how the master test suite is called. Each option is a super-set of the options before it. At this time we have:
  • minimal: This directory should include small, fast, and important tests which would should be run on every system.
  • default: This directory will include most tests which are not destructive, or particularly long to run. When a user runs with no flags, all tests in both default and minimal will be run.
  • stress: This directory will include longer running and more resource intensive tests which a user might not want to run in the common case due to time or resource constraints.
  • destructive: This directory contains tests which have a higher probability of causing harm to a system even in the pass case. This would include things like potential for data loss.
  • performance: This directory contains longer running performance tests. These tests should typically be the only load on a system to get an accurate result.

After Executing 
$ sudo ./runtests.sh -t performance
Each test is executed by the control script by calling runtest.sh. stdout and stderr are both redirected to the log. Any user running with default flags should see nothing but the name of the directory and pass/fail/skip. The runtest.sh should manage the full test run. This includes compiling any necessary source, checking for any specific dependencies, and skipping if they are not met. 



View the Log file with cat <file path> , the log file will give the device information and the test result.











The test is complete and the results is "PASS" in this case .







































Almost at the end of the file you will get the data and values of the tests.

Comments

Post a Comment

Popular posts from this blog

Rocket on Fedora

By -
Image
This post is a very small example of how you can start creating small web apps with Rocket which extensively uses Rust under the hood. This post will just give an idea about how to get started if you are totally new to rust. Rocket is a web framework for Rust that makes it simple to write fast web applications without sacrificing flexibility or type safety . All with minimal code. - rocket.rs Getting started: Start by installing rust nightly on your system or virtual box: $ curl -sSf https://static.rust-lang.org/rustup.sh | sh -s -- --channel=nightly                  Setting up Project and Dependencies: Setting up the project is easy cas you can go ahead and execute cargo new hello-rocket --bin Once the execution is completes , you will have a binary application created with a Cargo.toml file and src dir with main.rs inside it. For setting up the dependencies you need to update the Cargo.toml file. Now,it's time to update the source main.rs f
Read more

Tales from GNOME Asia 2023

By -
Image
Epilogue The GNOME Asia 2023 Summit, a key event in the open-source technology calendar, took place in Kathmandu, Nepal, from December 1 to 3, 2023. This conference is the premier annual event for the GNOME community in Asia, focusing on the GNOME desktop, applications, and development tools. The GNOME Foundation, which oversees this summit, aims to bring together various stakeholders, including users, developers, foundation leaders, government representatives, and businesses, to discuss present technologies and future developments. This iteration of the GNOME summit (as will be covered in the report) will have two parts, the community and the actual event proceedings. GNOME Asia Summit brought back the key FOSS stakeholders of Nepal into the limelight and also collaborated with the Fedora Project - helping them host a Release Party for Fedora Linux 39 and Celebrate the 20th year of the Fedora Project. Day 0  Like all "great" FOSS Projects do, Day 0 is all about intense colla
Read more

[Test Day Annoucement] Anaconda Blivet GUI

By -
Image
Thursday 2017-04-06 will be Anaconda Blivet-GUI Test Day ! As part of this planned Change for Fedora 26, So this is an important Test Day! We'll be testing the new detailed bottom-up configuration screen has been long requested by users and inclusion of blivet-gui into Anaconda finally makes this a reality. On the other hand, it just adds a new option without changing the existing advanced storage configuration so users that prefer the top-down configuration can still use it. to see whether it's working well enough and catch any remaining issues. It's also pretty easy to join in: all you'll need is alpha 1.7 (which you can grab from the wiki page). Anaconda grew a rather important new option in F26: as well as the two existing partitioning choices (automatic, and the existing anaconda custom part interface) there's now a *third* choice.so now you can do custom partitioning with blivet-gui run within anaconda, as well as using anaconda's own interface
Read more