lib/crypto/s390/sha512.h

File Facts

System

Linux kernel

Corpus path

lib/crypto/s390/sha512.h

Extension

.h

Size

809 bytes

Lines

29

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/cpacf.h
• linux/cpufeature.h

Detected Declarations

• function sha512_blocks
• function sha512_mod_init_arch

Annotated Snippet

#include <asm/cpacf.h>
#include <linux/cpufeature.h>

static __ro_after_init DEFINE_STATIC_KEY_FALSE(have_cpacf_sha512);

static void sha512_blocks(struct sha512_block_state *state,
			  const u8 *data, size_t nblocks)
{
	if (static_branch_likely(&have_cpacf_sha512))
		cpacf_kimd(CPACF_KIMD_SHA_512, state, data,
			   nblocks * SHA512_BLOCK_SIZE);
	else
		sha512_blocks_generic(state, data, nblocks);
}

#define sha512_mod_init_arch sha512_mod_init_arch
static void sha512_mod_init_arch(void)
{
	if (cpu_have_feature(S390_CPU_FEATURE_MSA) &&
	    cpacf_query_func(CPACF_KIMD, CPACF_KIMD_SHA_512))
		static_branch_enable(&have_cpacf_sha512);
}

Annotation

• Immediate include surface: `asm/cpacf.h`, `linux/cpufeature.h`.
• Detected declarations: `function sha512_blocks`, `function sha512_mod_init_arch`.
• 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.