tools/testing/selftests/powerpc/tm/tm-syscall-asm.S

File Facts

System

Linux kernel

Corpus path

tools/testing/selftests/powerpc/tm/tm-syscall-asm.S

Extension

.S

Size

754 bytes

Lines

64

Domain

Support Tooling And Documentation

Bucket

tools

Inferred role

Support Tooling And Documentation: syscall or user/kernel boundary

Status

core 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 participates in a user/kernel boundary; inspect argument validation, copy_from_user/copy_to_user, credentials, and dispatch target.

Dependency Surface

• basic_asm.h
• asm/unistd.h

Detected Declarations

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

Annotated Snippet

#include <basic_asm.h>
#include <asm/unistd.h>

	.text
FUNC_START(getppid_tm_active)
	tbegin.
	beq 1f
	li	r0, __NR_getppid
	sc
	tend.
	blr
1:
	li	r3, -1
	blr

FUNC_START(getppid_tm_suspended)
	tbegin.
	beq 1f
	li	r0, __NR_getppid
	tsuspend.
	sc
	tresume.
	tend.
	blr
1:
	li	r3, -1
	blr


.macro scv level
	.long (0x44000001 | (\level) << 5)
.endm

FUNC_START(getppid_scv_tm_active)
	PUSH_BASIC_STACK(0)
	tbegin.
	beq 1f
	li	r0, __NR_getppid
	scv	0
	tend.
	POP_BASIC_STACK(0)
	blr
1:
	li	r3, -1
	POP_BASIC_STACK(0)
	blr

FUNC_START(getppid_scv_tm_suspended)
	PUSH_BASIC_STACK(0)
	tbegin.
	beq 1f
	li	r0, __NR_getppid
	tsuspend.
	scv	0
	tresume.
	tend.
	POP_BASIC_STACK(0)
	blr
1:
	li	r3, -1
	POP_BASIC_STACK(0)
	blr

Annotation

• Immediate include surface: `basic_asm.h`, `asm/unistd.h`.
• Atlas domain: Support Tooling And Documentation / tools.
• Implementation status: core 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.