# dynticks-testing

**Repository Path**: mirrors_kernel_googlesource/dynticks-testing

## Basic Information

- **Project Name**: dynticks-testing
- **Description**: No description available
- **Primary Language**: Unknown
- **License**: Not specified
- **Default Branch**: master
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 0
- **Created**: 2021-03-19
- **Last Updated**: 2025-12-14

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

Make sure CPU 1 is full dynticks (it must be in the "nohz_full=" boot parameter
cpu mask).

To run:
	$ make
	# ./run

Look at the resulting trace in trace.1
hrtimer events should report you the tick events (unless you haven't
CONFIG_HIGH_RES_TIMERS=y) and tick_stop events tell you what's going on with full dynticks
behaviour.

trace.1.example shows an example of a successful full dynticks behaviour. The
tick got mostly stopped during the execution of the user loop.