| Kconfig (9938b04472d5c59f8bd8152a548533a8599596a2) | Kconfig (08d43a5fa063e03c860f2f391a30c388bcbc948e) |
|---|---|
| 1# 2# Architectures that offer an FUNCTION_TRACER implementation should 3# select HAVE_FUNCTION_TRACER: 4# 5 6config USER_STACKTRACE_SUPPORT 7 bool 8 --- 514 unchanged lines hidden (view full) --- 523 Mmiotrace traces Memory Mapped I/O access and is meant for 524 debugging and reverse engineering. It is called from the ioremap 525 implementation and works via page faults. Tracing is disabled by 526 default and can be enabled at run-time. 527 528 See Documentation/trace/mmiotrace.txt. 529 If you are not helping to develop drivers, say N. 530 | 1# 2# Architectures that offer an FUNCTION_TRACER implementation should 3# select HAVE_FUNCTION_TRACER: 4# 5 6config USER_STACKTRACE_SUPPORT 7 bool 8 --- 514 unchanged lines hidden (view full) --- 523 Mmiotrace traces Memory Mapped I/O access and is meant for 524 debugging and reverse engineering. It is called from the ioremap 525 implementation and works via page faults. Tracing is disabled by 526 default and can be enabled at run-time. 527 528 See Documentation/trace/mmiotrace.txt. 529 If you are not helping to develop drivers, say N. 530 |
| 531config TRACING_MAP 532 bool 533 depends on ARCH_HAVE_NMI_SAFE_CMPXCHG 534 default n 535 help 536 tracing_map is a special-purpose lock-free map for tracing, 537 separated out as a stand-alone facility in order to allow it 538 to be shared between multiple tracers. It isn't meant to be 539 generally used outside of that context, and is normally 540 selected by tracers that use it. 541 542 If in doubt, say N. 543 |
|
| 531config MMIOTRACE_TEST 532 tristate "Test module for mmiotrace" 533 depends on MMIOTRACE && m 534 help 535 This is a dumb module for testing mmiotrace. It is very dangerous 536 as it will write garbage to IO memory starting at a given address. 537 However, it should be safe to use on e.g. unused portion of VRAM. 538 --- 110 unchanged lines hidden --- | 544config MMIOTRACE_TEST 545 tristate "Test module for mmiotrace" 546 depends on MMIOTRACE && m 547 help 548 This is a dumb module for testing mmiotrace. It is very dangerous 549 as it will write garbage to IO memory starting at a given address. 550 However, it should be safe to use on e.g. unused portion of VRAM. 551 --- 110 unchanged lines hidden --- |