tools/power/cpupower/utils/powercap-info.c

File Facts

System

Linux kernel

Corpus path

tools/power/cpupower/utils/powercap-info.c

Extension

.c

Size

2209 bytes

Lines

118

Domain

Support Tooling And Documentation

Bucket

tools

Inferred role

Support Tooling And Documentation: implementation source

Status

source implementation candidate

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• unistd.h
• stdio.h
• errno.h
• stdlib.h
• stdint.h
• string.h
• getopt.h
• powercap.h
• helpers/helpers.h

Detected Declarations

• function powercap_print_one_zone
• function powercap_show
• function cmd_cap_set
• function cmd_cap_info

Annotated Snippet

switch (ret) {
		case '?':
			cont = 0;
			break;
		case -1:
			cont = 0;
			break;
		case 'a':
			powercap_show_all = 1;
			break;
		default:
			fprintf(stderr, _("invalid or unknown argument\n"));
			return EXIT_FAILURE;
		}
	} while (cont);

	powercap_show();
	return 0;
}

Annotation

• Immediate include surface: `unistd.h`, `stdio.h`, `errno.h`, `stdlib.h`, `stdint.h`, `string.h`, `getopt.h`, `powercap.h`.
• Detected declarations: `function powercap_print_one_zone`, `function powercap_show`, `function cmd_cap_set`, `function cmd_cap_info`.
• Atlas domain: Support Tooling And Documentation / tools.
• Implementation status: source implementation candidate.

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.