arch/x86/crypto/camellia_aesni_avx2_glue.c

File Facts

System

Linux kernel

Corpus path

arch/x86/crypto/camellia_aesni_avx2_glue.c

Extension

.c

Size

4055 bytes

Lines

132

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

• crypto/algapi.h
• linux/crypto.h
• linux/err.h
• linux/module.h
• linux/types.h
• camellia.h
• ecb_cbc_helpers.h

Detected Declarations

• function camellia_setkey
• function ecb_encrypt
• function ecb_decrypt
• function cbc_encrypt
• function cbc_decrypt
• function camellia_aesni_init
• function camellia_aesni_fini
• module init camellia_aesni_init

Annotated Snippet

module_init(camellia_aesni_init);
module_exit(camellia_aesni_fini);

MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("Camellia Cipher Algorithm, AES-NI/AVX2 optimized");
MODULE_ALIAS_CRYPTO("camellia");
MODULE_ALIAS_CRYPTO("camellia-asm");

Annotation

• Immediate include surface: `crypto/algapi.h`, `linux/crypto.h`, `linux/err.h`, `linux/module.h`, `linux/types.h`, `camellia.h`, `ecb_cbc_helpers.h`.
• Detected declarations: `function camellia_setkey`, `function ecb_encrypt`, `function ecb_decrypt`, `function cbc_encrypt`, `function cbc_decrypt`, `function camellia_aesni_init`, `function camellia_aesni_fini`, `module init camellia_aesni_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.