tools/power/acpi/man/acpidump.8

File Facts

System

Linux kernel

Corpus path

tools/power/acpi/man/acpidump.8

Extension

.8

Size

2528 bytes

Lines

128

Domain

Support Tooling And Documentation

Bucket

tools

Inferred role

Support Tooling And Documentation: tools

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

.TH ACPIDUMP 8
.SH NAME
acpidump \- dump a system's ACPI tables to an ASCII file

.SH SYNOPSIS
.B acpidump
.RI [ options ]
.br

.SH DESCRIPTION
.B acpidump
dumps the systems ACPI tables to an ASCII file appropriate for
attaching to a bug report.

Subsequently, they can be processed by utilities in the ACPICA package.

.SH OPTIONS
acpidump options are as follow:
.TP
.B Options
.TP
.B \-b
Dump tables to binary files
.TP
.B \-h \-?
This help message
.TP
.B \-o <File>
Redirect output to file
.TP
.B \-r <Address>
Dump tables from specified RSDP
.TP
.B \-s
Print table summaries only
.TP
.B \-v
Display version information
.TP
.B \-z
Verbose mode
.TP
.B Table Options
.TP
.B \-a <Address>
Get table via a physical address
.TP
.B \-c <on|off>
Turning on/off customized table dumping
.TP
.B \-f <BinaryFile>
Get table via a binary file
.TP
.B \-n <Signature>
Get table via a name/signature
.TP
.B \-x
Do not use but dump XSDT
.TP
.B \-x \-x
Do not use or dump XSDT
.TP
.fi
Invocation without parameters dumps all available tables.
.TP
Multiple mixed instances of -a, -f, and -n are supported.

.SH EXAMPLES

.nf

Annotation

• Atlas domain: Support Tooling And Documentation / tools.
• 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.