lib/raid/xor/sparc/xor_arch.h

File Facts

System

Linux kernel

Corpus path

lib/raid/xor/sparc/xor_arch.h

Extension

.h

Size

1041 bytes

Lines

36

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/spitfire.h

Detected Declarations

• function arch_xor_init
• function arch_xor_init

Annotated Snippet

#if defined(__sparc__) && defined(__arch64__)
#include <asm/spitfire.h>

extern struct xor_block_template xor_block_VIS;
extern struct xor_block_template xor_block_niagara;

static __always_inline void __init arch_xor_init(void)
{
	/* Force VIS for everything except Niagara.  */
	if (tlb_type == hypervisor &&
	    (sun4v_chip_type == SUN4V_CHIP_NIAGARA1 ||
	     sun4v_chip_type == SUN4V_CHIP_NIAGARA2 ||
	     sun4v_chip_type == SUN4V_CHIP_NIAGARA3 ||
	     sun4v_chip_type == SUN4V_CHIP_NIAGARA4 ||
	     sun4v_chip_type == SUN4V_CHIP_NIAGARA5))
		xor_force(&xor_block_niagara);
	else
		xor_force(&xor_block_VIS);
}
#else /* sparc64 */

extern struct xor_block_template xor_block_SPARC;

static __always_inline void __init arch_xor_init(void)
{
	xor_register(&xor_block_8regs);
	xor_register(&xor_block_32regs);
	xor_register(&xor_block_SPARC);
}
#endif /* !sparc64 */

Annotation

• Immediate include surface: `asm/spitfire.h`.
• Detected declarations: `function arch_xor_init`, `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.