arch/microblaze/kernel/reset.c
Source file repositories/reference/linux-study-clean/arch/microblaze/kernel/reset.c
File Facts
- System
- Linux kernel
- Corpus path
arch/microblaze/kernel/reset.c- Extension
.c- Size
- 778 bytes
- Lines
- 43
- Domain
- Architecture Layer
- Bucket
- arch/microblaze
- 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.
Dependency Surface
linux/init.hlinux/delay.hlinux/reboot.h
Detected Declarations
function Copyrightfunction machine_haltfunction machine_power_offfunction machine_restart
Annotated Snippet
#include <linux/init.h>
#include <linux/delay.h>
#include <linux/reboot.h>
void machine_shutdown(void)
{
pr_notice("Machine shutdown...\n");
while (1)
;
}
void machine_halt(void)
{
pr_notice("Machine halt...\n");
while (1)
;
}
void machine_power_off(void)
{
pr_notice("Machine power off...\n");
while (1)
;
}
void machine_restart(char *cmd)
{
do_kernel_restart(cmd);
/* Give the restart hook 1 s to take us down */
mdelay(1000);
pr_emerg("Reboot failed -- System halted\n");
while (1);
}
Annotation
- Immediate include surface: `linux/init.h`, `linux/delay.h`, `linux/reboot.h`.
- Detected declarations: `function Copyright`, `function machine_halt`, `function machine_power_off`, `function machine_restart`.
- Atlas domain: Architecture Layer / arch/microblaze.
- 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.