Instructions on how to run the Intel GPU Tools test suite on R-Car platforms, using the R-Car M3-W Salvator-X board as an example.
To run the test suite, it is necessary to create an ARM64 NFS root file system, install additional distribution packages as well as clone two git repositories for intel-gpu-tools and piglit. The individual steps are as follows:
On the engineer's workstation
- Create an ARM64 Debian root file system:
sudo qemu-debootstrap arch arm64 sid /tmp/repro_root http://deb.debian.org/debian/
- Copy File:Igt selections.txt as igt_selections to the file system just created in /tmp/repro_root.
On the target platform
The file system created in the previous step should now be booted on the target platform as an NFS root file system. The following steps should then be performed on the target platform:
- Connect an HDMI display to port HDMI0 on the M3-W Salvator-X board.
apt-get install dselect
dpkg --set-selections <igt_selections
apt-get dselect-upgrade -y
This will install all additional distribution packages required to run the IGT test suite and may therefore take a while.
- Create a UTF-8 locale: (This is required by the piglit tool.)
- Edit /etc/locale.gen and remove the comment character ("#") before the line that contains "en_US.UTF-8 UTF-8".
- To clone the intel-gpu-tools test suite, run these commands:
git clone git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
for the standard IGT distribution, OR
git clone https://github.com/uli/intel-gpu-tools.gitfor a version containing a number of fixes to obtain better test results on R-Car.
- To build the IGT test suite, run these commands:
cd intel-gpu-tools ./autogen.sh make -j4This step will take an extended amount of time due to the low performance of the NFS root file system.
- Clone the current version of the piglit tool: (There is a version of piglit included in the Debian distribution, but it is not recent enough to work with the IGT test suite.)
git clone git://anongit.freedesktop.org/piglit export PATH=`pwd`/piglit:$PATH
- Run the IGT test suite:
./scripts/run-tests.sh -x drv_module_reload -x drv_suspend -x @gem_concurrent -sNote that this command excludes driver reloading tests (which are not supported when using a statically compiled driver) as well as all tests starting with "gem_concurrent". These tests are very numerous (more than 50000) and are all not applicable to the DU device, so excluding them from the outset saves a lot of time.
A renesas-drivers kernel (renesas-drivers-2018-01-30-v4.15-1) has been used during development, configured with the default configuration (renesas_defconfig), and with the option CONFIG_SW_SYNC enabled.