arch/riscv/crypto/sm4-riscv64-glue.c

File Facts

System

Linux kernel

Corpus path

arch/riscv/crypto/sm4-riscv64-glue.c

Extension

.c

Size

2848 bytes

Lines

108

Domain

Architecture Layer

Bucket

arch/riscv

Inferred role

Architecture Layer: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.

• CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• asm/simd.h
• asm/vector.h
• crypto/internal/cipher.h
• crypto/internal/simd.h
• crypto/sm4.h
• linux/linkage.h
• linux/module.h

Detected Declarations

• function riscv64_sm4_setkey
• function riscv64_sm4_encrypt
• function riscv64_sm4_decrypt
• function riscv64_sm4_mod_init
• function riscv64_sm4_mod_exit
• module init riscv64_sm4_mod_init

Annotated Snippet

module_init(riscv64_sm4_mod_init);
module_exit(riscv64_sm4_mod_exit);

MODULE_DESCRIPTION("SM4 (RISC-V accelerated)");
MODULE_AUTHOR("Heiko Stuebner <heiko.stuebner@vrull.eu>");
MODULE_LICENSE("GPL");
MODULE_ALIAS_CRYPTO("sm4");

Annotation

• Immediate include surface: `asm/simd.h`, `asm/vector.h`, `crypto/internal/cipher.h`, `crypto/internal/simd.h`, `crypto/sm4.h`, `linux/linkage.h`, `linux/module.h`.
• Detected declarations: `function riscv64_sm4_setkey`, `function riscv64_sm4_encrypt`, `function riscv64_sm4_decrypt`, `function riscv64_sm4_mod_init`, `function riscv64_sm4_mod_exit`, `module init riscv64_sm4_mod_init`.
• Atlas domain: Architecture Layer / arch/riscv.
• Implementation status: integration 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.