arch/hexagon/kernel/syscalltab.c

File Facts

System

Linux kernel

Corpus path

arch/hexagon/kernel/syscalltab.c

Extension

.c

Size

785 bytes

Lines

31

Domain

Architecture Layer

Bucket

arch/hexagon

Inferred role

Architecture Layer: syscall or user/kernel boundary

Status

core 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.
• Defines or participates in a user/kernel boundary; inspect argument validation, copy_from_user/copy_to_user, credentials, and dispatch target.

Dependency Surface

• linux/syscalls.h
• linux/signal.h
• linux/unistd.h
• asm/syscall.h
• asm/syscall_table_32.h

Detected Declarations

• syscall hexagon_fadvise64_64
• function Copyright

Annotated Snippet

SYSCALL_DEFINE6(hexagon_fadvise64_64, int, fd, int, advice,
		SC_ARG64(offset), SC_ARG64(len))
{
	return ksys_fadvise64_64(fd, SC_VAL64(loff_t, offset), SC_VAL64(loff_t, len), advice);
}
#define sys_fadvise64_64 sys_hexagon_fadvise64_64

#define sys_sync_file_range sys_sync_file_range2

void *sys_call_table[__NR_syscalls] = {
#include <asm/syscall_table_32.h>
};

Annotation

• Immediate include surface: `linux/syscalls.h`, `linux/signal.h`, `linux/unistd.h`, `asm/syscall.h`, `asm/syscall_table_32.h`.
• Detected declarations: `syscall hexagon_fadvise64_64`, `function Copyright`.
• Atlas domain: Architecture Layer / arch/hexagon.
• Implementation status: core 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.