CONFIG_MMIOTRACE: Memory mapped IO tracing

General informations

The Linux kernel configuration item CONFIG_MMIOTRACE has multiple definitions:

Memory mapped IO tracing found in kernel/trace/Kconfig

The configuration item CONFIG_MMIOTRACE:

• prompt: Memory mapped IO tracing
• type: bool
• depends on: CONFIG_HAVE_MMIOTRACE_SUPPORT && CONFIG_PCI
• defined in kernel/trace/Kconfig
• found in Linux kernels: 2.6.29–2.6.39, 3.0–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.12, 6.13-rc+HEAD

Help text

Mmiotrace traces Memory Mapped I/O access and is meant for debugging and reverse engineering. It is called from the ioremap implementation and works via page faults. Tracing is disabled by default and can be enabled at run-time.

See Documentation/trace/mmiotrace.rst. If you are not helping to develop drivers, say N.

Memory mapped IO tracing found in arch/x86/Kconfig.debug

The configuration item CONFIG_MMIOTRACE:

• prompt: Memory mapped IO tracing
• type: bool
• depends on: CONFIG_DEBUG_KERNEL && CONFIG_PCI
• defined in arch/x86/Kconfig.debug
• found in Linux kernels: 2.6.27–2.6.28

Help text

Mmiotrace traces Memory Mapped I/O access and is meant for debugging and reverse engineering. It is called from the ioremap implementation and works via page faults. Tracing is disabled by default and can be enabled at run-time.

See Documentation/tracers/mmiotrace.txt. If you are not helping to develop drivers, say N.

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: