lib/crypto/x86/sm3.h
Source file repositories/reference/linux-study-clean/lib/crypto/x86/sm3.h
File Facts
- System
- Linux kernel
- Corpus path
lib/crypto/x86/sm3.h- Extension
.h- Size
- 1041 bytes
- Lines
- 40
- 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/fpu/api.hlinux/static_call.h
Detected Declarations
function sm3_blocks_avxfunction sm3_blocksfunction sm3_mod_init_arch
Annotated Snippet
#include <asm/fpu/api.h>
#include <linux/static_call.h>
asmlinkage void sm3_transform_avx(struct sm3_block_state *state,
const u8 *data, size_t nblocks);
static void sm3_blocks_avx(struct sm3_block_state *state,
const u8 *data, size_t nblocks)
{
if (likely(irq_fpu_usable())) {
kernel_fpu_begin();
sm3_transform_avx(state, data, nblocks);
kernel_fpu_end();
} else {
sm3_blocks_generic(state, data, nblocks);
}
}
DEFINE_STATIC_CALL(sm3_blocks_x86, sm3_blocks_generic);
static void sm3_blocks(struct sm3_block_state *state,
const u8 *data, size_t nblocks)
{
static_call(sm3_blocks_x86)(state, data, nblocks);
}
#define sm3_mod_init_arch sm3_mod_init_arch
static void sm3_mod_init_arch(void)
{
if (boot_cpu_has(X86_FEATURE_AVX) && boot_cpu_has(X86_FEATURE_BMI2) &&
cpu_has_xfeatures(XFEATURE_MASK_SSE | XFEATURE_MASK_YMM, NULL))
static_call_update(sm3_blocks_x86, sm3_blocks_avx);
}
Annotation
- Immediate include surface: `asm/fpu/api.h`, `linux/static_call.h`.
- Detected declarations: `function sm3_blocks_avx`, `function sm3_blocks`, `function sm3_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.