tools/testing/selftests/arm64/signal/testcases/mangle_pstate_invalid_mode_template.h

File Facts

System

Linux kernel

Corpus path

tools/testing/selftests/arm64/signal/testcases/mangle_pstate_invalid_mode_template.h

Extension

.h

Size

803 bytes

Lines

29

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

• 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

#define DEFINE_TESTCASE_MANGLE_PSTATE_INVALID_MODE(_mode)		\
									\
static int mangle_invalid_pstate_run(struct tdescr *td, siginfo_t *si,	\
				     ucontext_t *uc)			\
{									\
	ASSERT_GOOD_CONTEXT(uc);					\
									\
	uc->uc_mcontext.pstate &= ~PSR_MODE_MASK;			\
	uc->uc_mcontext.pstate |= PSR_MODE_EL ## _mode;			\
									\
	return 1;							\
}									\
									\
struct tdescr tde = {							\
		.sanity_disabled = true,				\
		.name = "MANGLE_PSTATE_INVALID_MODE_EL"#_mode,		\
		.descr = "Mangling uc_mcontext INVALID MODE EL"#_mode,	\
		.sig_trig = SIGUSR1,					\
		.sig_ok = SIGSEGV,					\
		.run = mangle_invalid_pstate_run,			\
}

Annotation

• 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.