CONFIG_CONTEXT_TRACKING_FORCE: Force context tracking

General informations

The Linux kernel configuration item CONFIG_CONTEXT_TRACKING_FORCE has multiple definitions:

Force context tracking found in kernel/time/Kconfig

The configuration item CONFIG_CONTEXT_TRACKING_FORCE:

• prompt: Force context tracking
• type: bool
• depends on: ( CONFIG_CONTEXT_TRACKING ) && (! CONFIG_NO_HZ_FULL )
• defined in kernel/time/Kconfig
• found in Linux kernels: 5.1–5.19, 5.19+HEAD

Help text

The major pre-requirement for full dynticks to work is to support the context tracking subsystem. But there are also other dependencies to provide in order to make the full dynticks working.

This option stands for testing when an arch implements the context tracking backend but doesn't yet fulfill all the requirements to make the full dynticks feature working. Without the full dynticks, there is no way to test the support for context tracking and the subsystems that rely on it: RCU userspace extended quiescent state and tickless cputime accounting. This option copes with the absence of the full dynticks subsystem by forcing the context tracking on all CPUs in the system.

Say Y only if you're working on the development of an architecture backend for the context tracking.

Say N otherwise, this option brings an overhead that you don't want in production.

Force context tracking found in kernel/rcu/Kconfig

The configuration item CONFIG_CONTEXT_TRACKING_FORCE:

• prompt: Force context tracking
• type: bool
• depends on: ( CONFIG_CONTEXT_TRACKING ) && (! CONFIG_NO_HZ_FULL )
• defined in kernel/rcu/Kconfig
• found in Linux kernels: 4.13–4.20, 5.0

Help text

The major pre-requirement for full dynticks to work is to support the context tracking subsystem. But there are also other dependencies to provide in order to make the full dynticks working.

This option stands for testing when an arch implements the context tracking backend but doesn't yet fullfill all the requirements to make the full dynticks feature working. Without the full dynticks, there is no way to test the support for context tracking and the subsystems that rely on it: RCU userspace extended quiescent state and tickless cputime accounting. This option copes with the absence of the full dynticks subsystem by forcing the context tracking on all CPUs in the system.

Say Y only if you're working on the development of an architecture backend for the context tracking.

Say N otherwise, this option brings an overhead that you don't want in production.

Force context tracking found in init/Kconfig

The configuration item CONFIG_CONTEXT_TRACKING_FORCE:

• prompt: Force context tracking
• type: bool
• depends on: ( CONFIG_CONTEXT_TRACKING ) && (! CONFIG_NO_HZ_FULL )
• defined in init/Kconfig
• found in Linux kernels: 3.8–3.19, 4.0–4.12

Help text

The major pre-requirement for full dynticks to work is to support the context tracking subsystem. But there are also other dependencies to provide in order to make the full dynticks working.

This option stands for testing when an arch implements the context tracking backend but doesn't yet fullfill all the requirements to make the full dynticks feature working. Without the full dynticks, there is no way to test the support for context tracking and the subsystems that rely on it: RCU userspace extended quiescent state and tickless cputime accounting. This option copes with the absence of the full dynticks subsystem by forcing the context tracking on all CPUs in the system.

Say Y only if you're working on the development of an architecture backend for the context tracking.

Say N otherwise, this option brings an overhead that you don't want in production.

Hardware

LKDDb

Raw data from LKDDb:

• (none)

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: