arch/x86/crypto/sm4_aesni_avx2_glue.c

File Facts

System

Linux kernel

Corpus path

arch/x86/crypto/sm4_aesni_avx2_glue.c

Extension

.c

Size

3623 bytes

Lines

135

Domain

Architecture Layer

Bucket

arch/x86

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/fpu/api.h
• linux/module.h
• linux/crypto.h
• linux/kernel.h
• crypto/internal/skcipher.h
• crypto/sm4.h
• sm4-avx.h

Detected Declarations

• function sm4_skcipher_setkey
• function cbc_decrypt
• function ctr_crypt
• function sm4_init
• function sm4_exit
• module init sm4_init

Annotated Snippet

module_init(sm4_init);
module_exit(sm4_exit);

MODULE_LICENSE("GPL v2");
MODULE_AUTHOR("Tianjia Zhang <tianjia.zhang@linux.alibaba.com>");
MODULE_DESCRIPTION("SM4 Cipher Algorithm, AES-NI/AVX2 optimized");
MODULE_ALIAS_CRYPTO("sm4");
MODULE_ALIAS_CRYPTO("sm4-aesni-avx2");

Annotation

• Immediate include surface: `asm/fpu/api.h`, `linux/module.h`, `linux/crypto.h`, `linux/kernel.h`, `crypto/internal/skcipher.h`, `crypto/sm4.h`, `sm4-avx.h`.
• Detected declarations: `function sm4_skcipher_setkey`, `function cbc_decrypt`, `function ctr_crypt`, `function sm4_init`, `function sm4_exit`, `module init sm4_init`.
• Atlas domain: Architecture Layer / arch/x86.
• 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.