arch/microblaze/kernel/sys_microblaze.c

File Facts

System

Linux kernel

Corpus path

arch/microblaze/kernel/sys_microblaze.c

Extension

.c

Size

1541 bytes

Lines

56

Domain

Architecture Layer

Bucket

arch/microblaze

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/export.h
• linux/mm.h
• linux/smp.h
• linux/syscalls.h
• linux/sem.h
• linux/msg.h
• linux/shm.h
• linux/stat.h
• linux/mman.h
• linux/sys.h
• linux/ipc.h
• linux/file.h
• linux/err.h
• linux/fs.h
• linux/semaphore.h
• linux/uaccess.h
• linux/unistd.h
• linux/slab.h
• asm/syscalls.h

Detected Declarations

• syscall mmap
• syscall mmap2
• function Copyright

Annotated Snippet

SYSCALL_DEFINE6(mmap, unsigned long, addr, unsigned long, len,
		unsigned long, prot, unsigned long, flags, unsigned long, fd,
		unsigned long, pgoff)
{
	if (pgoff & ~PAGE_MASK)
		return -EINVAL;

	return ksys_mmap_pgoff(addr, len, prot, flags, fd, pgoff >> PAGE_SHIFT);
}

SYSCALL_DEFINE6(mmap2, unsigned long, addr, unsigned long, len,
		unsigned long, prot, unsigned long, flags, unsigned long, fd,
		unsigned long, pgoff)
{
	if (pgoff & (~PAGE_MASK >> 12))
		return -EINVAL;

	return ksys_mmap_pgoff(addr, len, prot, flags, fd,
			       pgoff >> (PAGE_SHIFT - 12));
}

Annotation

• Immediate include surface: `linux/errno.h`, `linux/export.h`, `linux/mm.h`, `linux/smp.h`, `linux/syscalls.h`, `linux/sem.h`, `linux/msg.h`, `linux/shm.h`.
• Detected declarations: `syscall mmap`, `syscall mmap2`, `function Copyright`.
• Atlas domain: Architecture Layer / arch/microblaze.
• 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.