Documentation/ABI/testing/debugfs-hyperv

Source file repositories/reference/linux-study-clean/Documentation/ABI/testing/debugfs-hyperv

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/testing/debugfs-hyperv
Extension: [no extension]
Size: 963 bytes
Lines: 24
Domain: Support Tooling And Documentation
Bucket: Documentation
Inferred role: Support Tooling And Documentation: Documentation
Status: atlas-only

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Dependency Surface

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

What:           /sys/kernel/debug/hyperv/<UUID>/fuzz_test_state
Date:           October 2019
KernelVersion:  5.5
Contact:        Branden Bonaby <brandonbonaby94@gmail.com>
Description:    Fuzz testing status of a vmbus device, whether its in an ON
                state or a OFF state
Users:          Debugging tools

What:           /sys/kernel/debug/hyperv/<UUID>/delay/fuzz_test_buffer_interrupt_delay
Date:           October 2019
KernelVersion:  5.5
Contact:        Branden Bonaby <brandonbonaby94@gmail.com>
Description:    Fuzz testing buffer interrupt delay value between 0 - 1000
		 microseconds (inclusive).
Users:          Debugging tools

What:           /sys/kernel/debug/hyperv/<UUID>/delay/fuzz_test_message_delay
Date:           October 2019
KernelVersion:  5.5
Contact:        Branden Bonaby <brandonbonaby94@gmail.com>
Description:    Fuzz testing message delay value between 0 - 1000 microseconds
		 (inclusive).
Users:          Debugging tools

Annotation

Atlas domain: Support Tooling And Documentation / Documentation.
Implementation status: atlas-only.

Implementation Notes

This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.