arch/mips/sgi-ip32/ip32-berr.c
Source file repositories/reference/linux-study-clean/arch/mips/sgi-ip32/ip32-berr.c
File Facts
- System
- Linux kernel
- Corpus path
arch/mips/sgi-ip32/ip32-berr.c- Extension
.c- Size
- 973 bytes
- Lines
- 41
- Domain
- Architecture Layer
- Bucket
- arch/mips
- Inferred role
- Architecture Layer: implementation source
- Status
- source 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 uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/init.hlinux/kernel.hlinux/sched.hlinux/sched/debug.hlinux/sched/signal.hasm/traps.hlinux/uaccess.hasm/addrspace.hasm/ptrace.hasm/tlbdebug.hip32-common.h
Detected Declarations
function Copyrightfunction ip32_be_init
Annotated Snippet
#include <linux/init.h>
#include <linux/kernel.h>
#include <linux/sched.h>
#include <linux/sched/debug.h>
#include <linux/sched/signal.h>
#include <asm/traps.h>
#include <linux/uaccess.h>
#include <asm/addrspace.h>
#include <asm/ptrace.h>
#include <asm/tlbdebug.h>
#include "ip32-common.h"
static int ip32_be_handler(struct pt_regs *regs, int is_fixup)
{
int data = regs->cp0_cause & 4;
if (is_fixup)
return MIPS_BE_FIXUP;
printk("Got %cbe at 0x%lx\n", data ? 'd' : 'i', regs->cp0_epc);
show_regs(regs);
dump_tlb_all();
while(1);
force_sig(SIGBUS);
}
void __init ip32_be_init(void)
{
mips_set_be_handler(ip32_be_handler);
}
Annotation
- Immediate include surface: `linux/init.h`, `linux/kernel.h`, `linux/sched.h`, `linux/sched/debug.h`, `linux/sched/signal.h`, `asm/traps.h`, `linux/uaccess.h`, `asm/addrspace.h`.
- Detected declarations: `function Copyright`, `function ip32_be_init`.
- Atlas domain: Architecture Layer / arch/mips.
- Implementation status: source 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.