arch/sh/kernel/sys_sh32.c

File Facts

System

Linux kernel

Corpus path

arch/sh/kernel/sys_sh32.c

Extension

.c

Size

1898 bytes

Lines

73

Domain

Architecture Layer

Bucket

arch/sh

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/errno.h
• linux/sched.h
• linux/sched/task_stack.h
• linux/mm.h
• linux/smp.h
• linux/sem.h
• linux/msg.h
• linux/shm.h
• linux/stat.h
• linux/syscalls.h
• linux/mman.h
• linux/file.h
• linux/module.h
• linux/fs.h
• linux/ipc.h
• asm/cacheflush.h
• linux/uaccess.h
• asm/unistd.h
• asm/syscalls.h

Detected Declarations

• syscall sh_sync_file_range6
• function sys_pipe
• function sys_pread_wrapper
• function sys_pwrite_wrapper
• function sys_fadvise64_64_wrapper
• function SC_ARG64

Annotated Snippet

SYSCALL_DEFINE6(sh_sync_file_range6, int, fd, SC_ARG64(offset),
                SC_ARG64(nbytes), unsigned int, flags)
{
        return ksys_sync_file_range(fd, SC_VAL64(loff_t, offset),
                                    SC_VAL64(loff_t, nbytes), flags);
}

Annotation

• Immediate include surface: `linux/errno.h`, `linux/sched.h`, `linux/sched/task_stack.h`, `linux/mm.h`, `linux/smp.h`, `linux/sem.h`, `linux/msg.h`, `linux/shm.h`.
• Detected declarations: `syscall sh_sync_file_range6`, `function sys_pipe`, `function sys_pread_wrapper`, `function sys_pwrite_wrapper`, `function sys_fadvise64_64_wrapper`, `function SC_ARG64`.
• Atlas domain: Architecture Layer / arch/sh.
• 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.