• 2020
  • 06/18/2020
  • Public Content

Profiling Linux*, Android*, and QNX* System Boot Time

This recipe illustrates how to integrate
Intel® VTune™
performance analysis to the boot flow of Linux, Android, and QNX operating systems. This analysis helps to identify activities that execute unexpectedly long on CPU cores during the OS boot. This enables further boot order inspection.
When profiling boot time, you inject
Intel® VTune™
performance data collection command into the early stage of OS boot (either configured via init script or using a particular service). To achieve best results, ensure that these requirements are met:
  • Place
    Intel® VTune™
    data collector binary files in the earliest available file directory.
  • For Linux and Android OS data collector writes to the file system, the output file name must use the earliest available writable directory.
  • For Linux and Android OS, the VTune Amplifier data collection command should depend on file system availability. For QNX OS, the command should depend on network availability.
While this approach is suitable to address several problems during OS boot time, it cannot cover the entire boot process. For example, kernel decompression stage and file system mount stages are not covered.


This section lists the software used for the performance analysis scenario.
  • Operating system
    • Linux with the
      system initialization type. Root access is enabled.
    • QNX
  • Tools:
    • QNX* Momentics* Tool Suite
    • QNX 7.0 SDK
    • Intel® VTune™
      2019 (or newer)
    • For
      downloads and product support, visit
    • All the Cookbook recipes are scalable and can be applied to Intel VTune Amplifier 2018 and higher. Slight version-specific configuration changes are possible.
    • Intel® VTune™ Amplifier has been renamed to Intel® VTune™ Profiler starting with its version for Intel® oneAPI Base Toolkit (Beta). You can still use a standalone version of the VTune Profiler, or its versions integrated into Intel Parallel Studio XE or Intel System Studio.

Profile Linux System Boot Time via systemd

  • Install VTune Profiler on your target Linux system.
  • Check the type of system initialization. To confirm the system is using
    , enter:
    systemctl | grep "\-\.mount"
    The following output is expected if
    is used:
    -.mount loaded active mounted /
To profile Linux system boot time:
  1. Create a
    file and configure it to run a hardware analysis (Hotspots, I/O Analysis, and others) with
    Intel® VTune™
    For example, to execute the Hotspots analysis system-wide for 30 seconds using a low sampling interval for higher data precision, use:
    #!/bin/bash /opt/intel/vtune_amplifier/bin64/amplxe-cl -c hotspots -knob sampling-mode=hw -knob sampling-interval=0.1 -d 30 -finalization-mode=none -r /tmp/boot_profile &
    • Make sure the path in the file correctly specifies the
      Intel® VTune™
      installation directory. By default, the installation directory on Linux is
    • The path to the
      script can be any local path available at early boot stages, for example:
  2. Change the permission for the data collection startup script:
    chmod 755 /boot_profile
  3. Create a
    file with the following content:
    [Unit] Description=VTune Profiler boot profile service [Service] Type=forking ExecStart=/boot_profile [Install]
  4. Enable the service:
    systemctl enable vtune_boot
  5. Reboot your system to start a
    Intel® VTune™
    data collection during the OS boot process.
When the data collection is completed, the result directory will be located in
. This directory is created under the
user. If you need to open a result under a regular user, change the folder permissions:
sudo chmod -R a+w /tmp/boot_profile
Additional commands:
  • To disable the service:
    systemctl disable vtune_boot
  • To analyze
    Intel® VTune™
    collector output during the OS boot process in case of any failures:
    sudo journalctl -u vtune_boot

Profile Android System Boot Time

  1. Install
    Intel® VTune™
    on your host system.
  2. Run the
    command on the target Android system to make sure Intel sampling drivers are available.
    If the drivers (
    ) are not present, you can either continue with driverless approach and skip the subsequent steps or you can build and sign the drivers as follows:
    1. Run the following command on your host system:
    2. When prompted, specify the path to the GCC* compiler and Android kernel source directory used to build the target system.
      For example, the kernel source directory is
      , and the compiler directory is
      Successfully built drivers are located in the following directories:
      • <
      • <
      • <
    3. Sign the drivers as follows:
      $KERNEL_DIR/scripts/sign-file $(CONFIG_MODULE_SIG_HASH) $KERNEL_DIR/$(CONFIG_MODULE_SIG_KEY) $KERNEL_DIR/certs/signing_key.x509 <driver_file_name.ko>
      is the name of the driver you sign. You have to sign each driver separately.
      Use the kernel
      file from
      to get values for
To profile Android system boot time:
  1. Install the
    Intel® VTune™
    target collector.
    1. Boot the target system in a normal manner.
    2. Run the
      Intel® VTune™
      GUI and create a new project.
    3. Configure a new analysis. In the WHERE field, select
      Android Device (ADB)
      as the connection type. Select the target device in the ADB destination field. From this point onwards,
      Intel® VTune™
      should automatically upload the target collector to the target system.
  2. Copy the target collector to the earliest available file system location (for example, to
    adb shell cp -rf /data/data/ /vendor/vtune
  3. If Intel sampling drivers are available, copy
    pax.ko, sep5.ko,
    drivers to
  4. Choose the earliest available writable location as the destination directory for the collected traces. For example, choose
    and create an executable script (
    ) with this content, using either Intel sampling drivers or driver-less mode:
    Driver mode
    Driver-less mode
    #!/bin/sh rm -rf /data/vtune mkdir /data/vtune 0777 /system/bin/insmod /vendor/vtune/pax.ko /system/bin/insmod /vendor/vtune/socperf3.ko /system/bin/insmod /vendor/vtune/sep5.ko LD_LIBRARY_PATH=/vendor/vtune/perfrun/lib64 SEP_BASE_DIR=/vendor/vtune/perfrun/lib64 /vendor/vtune/perfrun/bin64/sep - start -d 10 -out /data/vtune/android_boot.tb7
    #!/bin/sh rm -rf /data/vtune mkdir /data/vtune 0777 echo 0 > /proc/sys/kernel/perf_event_paranoid echo 0 > /proc/sys/kernel/kptr_restrict /vendor/vtune/perfrun/bin64/amplxe-perf record -a -o /data/vtune/ -- sleep 10
    This should start the Hotspots collection for 10 seconds.
  5. Add this section to
    on the target. Consider using post-fs or any other trigger depending on the actual boot flow:
    on fs start vtune service vtune /vendor/vtune/ user root group root seclabel u:r:init:s0 oneshot disabled
    If you have a read-only file system, consider changing these files on the host and building your Android system from the source code.
  6. Optionally, depending on the OS configuration, add these lines to the
    /system/bin/toolbox u:object_r:toolbox_exec:s0 + /system/bin/insmod u:object_r:toolbox_exec:s0 + /system/bin/sep u:object_r:toolbox_exec:s0 + /system/bin/sh u:object_r:toolbox_exec:s0
    Make sure your Android device is booted in the permissive mode.
  7. Reboot the target Android system and wait until data is collected.
  8. Copy the
    file to the host system for further analysis.

Profile QNX System Boot Time

  • Install QNX* Momentics* Tool Suite on your host.
  • Install QNX 7.0 SDK.
  • Import a BSP to your QNX Momentics workspace via
    QNX Source Package and BSP
  • Install VTune Profiler on your host system.
To profile QNX system boot time:
  1. Copy the target profiling agent (
    binary) from
  2. Modify a
    file of your QNX image.
    1. Find a string
      and add
      after it.
    2. Find a startup script section and add
      sep -p1 &
      [+script] startup-script = { ... # NOTE: Temporary enable for UART devices on OCP bridge # will be able to removed once ABL is fixed ocp_init -d 0:24:0 0x200=0xffff04b5 0x204=7 ocp_init -d 0:24:1 0x200=0xffff04b5 0x204=7 ocp_init -d 0:24:2 0x200=0xffff04b5 0x204=7 # console ocp_init -d 0:24:3 0x200=0xffff04b5 0x204=7 # the sep run before this could move system to unstable # state and crash it sep -p1 -d 10 &
      target profiling agent options are:
      • -p<
        configures the collection mode:
        sets regular default mode. The profiling agent waits for the connection from the host over TCP/IP.
        enables the agent to start a preconfigured collection without stacks. Collected samples are stored in the target memory. To transfer the data to the host, TCP/IP connection is required.
        enables the agent to start a preconfigured collection with sample call stacks. Collected samples are stored in the target memory. To transfer the data to the host, TCP/IP connection is required.
      • -d <
        sets the maximum duration of a collection (in seconds). The collection stops after the specified time or when the memory buffer is full.
      • -s <
        defers the start of a collection by the specified time.
      • -b <
        sets the collection buffer size (1 ^ size_ratio bytes); for a single CPU core, for example, specify
        -b 23
        for 8Mb buffer size. The agent uses a double-buffer schema for switching buffers so that the amount of target memory consumption per a CPU core would be 16Mb. In case of 4 CPU cores, the overall memory consumption by the agent would be 64Mb. The default value is 19 (0.5Mb).
  3. Rebuild and flash QNX image.
  4. Reboot your system to start a data collection with
    Intel® VTune™
    during OS boot process.
  5. Propagate the collection results to the host.
    In the preconfigured collection mode (
    ), the target agent profiles the workload for the specified duration inside the memory buffer and switches to the listening mode sending a message like this:
    'sep5_0: Waiting for control connection from host on port XXXX...' to console
    . After this, you can launch the
    utility on the host to copy the collected data from the target over the network. Make sure the host command line options you use correspond to the target agent options. For example, for the
    mode, the host command looks like this:
    <vtune-install-dir>/bin64/sep -start -target-ip <target-system-ip-address> -target-port 9321 -out /tmp/qnx_boot.tb7
    For the
    <vtune-install-dir>/bin64/sep -start -target-ip <target-system-ip-address> -target-port 9321 -lbr call_stack -out /tmp/qnx_boot.tb7

Import the Result to an
Intel® VTune™

  1. Launch the
    Intel® VTune™
    standalone GUI on the host system to pick up proper binary files during result finalization.
    For example, to launch
    Intel® VTune™
    on Windows OS, enter:
  2. Create a new VTune Profiler project and configure binary/symbol search directories to include paths for the debug files of the kernel and/or drivers.
    On a Linux host, you can change the kptr_restrict value to 0 to enable resolving kernel function names.
  3. Import your result to the project:
    • To import a Linux result, use the
      Import a result into the current project
      option. For example:
    • To import a result from Android or QNX, use the
      Import raw data
      option and click the browse button to select the required
      When the
      file is imported and the result is finalized, switch to the
      Hotspots by CPU Utilization

Analyze Process Execution

Open the result and click the Bottom-up tab to identify which processes occupied most of CPU resources:
Switch to the
tab and analyze a sequence of processes/services execution. To do this:
  1. Change the Timeline grouping to
  2. Right-click to open the context menu and sort the rows by
    Row Start Time
    in the
  3. Analyze a process execution order:

Product and Performance Information


Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.

Notice revision #20110804