lib/raid/xor/loongarch/xor_arch.h

File Facts

System

Linux kernel

Corpus path

lib/raid/xor/loongarch/xor_arch.h

Extension

.h

Size

952 bytes

Lines

34

Domain

Kernel Services

Bucket

lib

Inferred role

Kernel Services: implementation source

Status

source implementation candidate

Why This File Exists

Shared kernel service surface used by multiple subsystems, including helpers, cryptography, virtualization support, and async I/O infrastructure.

• Shared kernel service surface used by multiple subsystems, including helpers, cryptography, virtualization support, and async I/O infrastructure.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• asm/cpu-features.h

Detected Declarations

• function arch_xor_init

Annotated Snippet

#include <asm/cpu-features.h>

/*
 * For grins, also test the generic routines.
 *
 * More importantly: it cannot be ruled out at this point of time, that some
 * future (maybe reduced) models could run the vector algorithms slower than
 * the scalar ones, maybe for errata or micro-op reasons. It may be
 * appropriate to revisit this after one or two more uarch generations.
 */

extern struct xor_block_template xor_block_lsx;
extern struct xor_block_template xor_block_lasx;

static __always_inline void __init arch_xor_init(void)
{
	xor_register(&xor_block_8regs);
	xor_register(&xor_block_8regs_p);
	xor_register(&xor_block_32regs);
	xor_register(&xor_block_32regs_p);
#ifdef CONFIG_CPU_HAS_LSX
	if (cpu_has_lsx)
		xor_register(&xor_block_lsx);
#endif
#ifdef CONFIG_CPU_HAS_LASX
	if (cpu_has_lasx)
		xor_register(&xor_block_lasx);
#endif
}

Annotation

• Immediate include surface: `asm/cpu-features.h`.
• Detected declarations: `function arch_xor_init`.
• Atlas domain: Kernel Services / lib.
• 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.