CONFIG_DRM_XE_PREEMPT_TIMEOUT: Default preempt timeout (us, jiffy granularity)

General informations

The Linux kernel configuration item CONFIG_DRM_XE_PREEMPT_TIMEOUT has multiple definitions:

Default preempt timeout (us, jiffy granularity) found in drivers/gpu/drm/xe/Kconfig.profile

The configuration item CONFIG_DRM_XE_PREEMPT_TIMEOUT:

• prompt: Default preempt timeout (us, jiffy granularity)
• type: int
• depends on: (none)
• defined in drivers/gpu/drm/xe/Kconfig.profile
• found in Linux kernels: 7.3-rc+HEAD

Help text

Initial per-engine-class preemption timeout (in microseconds). This is the value the driver programs at boot; it can be changed at runtime via the sysfs preempt_timeout_us knob.

This is how long the driver waits for the current context to reach an arbitration point and yield the GPU voluntarily when a higher-priority context becomes runnable. If the context does not yield before the timer expires, the HW is reset to allow the higher-priority context to execute.

The range userspace may write via sysfs is bounded by DRM_XE_PREEMPT_TIMEOUT_MIN and DRM_XE_PREEMPT_TIMEOUT_MAX.

Preempt timeout (us, jiffy granularity) found in drivers/gpu/drm/xe/Kconfig.profile

The configuration item CONFIG_DRM_XE_PREEMPT_TIMEOUT:

• prompt: Preempt timeout (us, jiffy granularity)
• type: int
• depends on: (none)
• defined in drivers/gpu/drm/xe/Kconfig.profile
• found in Linux kernels: 6.8–6.19, 7.0–7.2

Help text

How long to wait (in microseconds) for a preemption event to occur when submitting a new context. If the current context does not hit an arbitration point and yield to HW before the timer expires, the HW will be reset to allow the more important context to execute.

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: