tools/testing/memblock/linux/printk.h

File Facts

System

Linux kernel

Corpus path

tools/testing/memblock/linux/printk.h

Extension

.h

Size

650 bytes

Lines

26

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.

Dependency Surface

• stdio.h
• asm/bug.h

Detected Declarations

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

Annotated Snippet

#ifndef _PRINTK_H
#define _PRINTK_H

#include <stdio.h>
#include <asm/bug.h>

/*
 * memblock_dbg is called with u64 arguments that don't match the "%llu"
 * specifier in printf. This results in warnings that cannot be fixed without
 * modifying memblock.c, which we wish to avoid. As these messaged are not used
 * in testing anyway, the mismatch can be ignored.
 */
#pragma GCC diagnostic push
#pragma GCC diagnostic ignored "-Wformat"
#define printk printf
#pragma GCC diagnostic push

#define pr_info printk
#define pr_debug printk
#define pr_cont printk
#define pr_err printk
#define pr_warn printk

#endif

Annotation

• Immediate include surface: `stdio.h`, `asm/bug.h`.
• 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.