arch/m68k/include/asm/mcfwdebug.h
Source file repositories/reference/linux-study-clean/arch/m68k/include/asm/mcfwdebug.h
File Facts
- System
- Linux kernel
- Corpus path
arch/m68k/include/asm/mcfwdebug.h- Extension
.h- Size
- 5106 bytes
- Lines
- 120
- Domain
- Architecture Layer
- Bucket
- arch/m68k
- 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
- No C-style include directives detected by the generator.
Detected Declarations
function instructions
Annotated Snippet
static inline void wdebug(int reg, unsigned long data) {
unsigned short dbg_spc[6];
unsigned short *dbg;
// Force alignment to long word boundary
dbg = (unsigned short *)((((unsigned long)dbg_spc) + 3) & 0xfffffffc);
// Build up the debug instruction
dbg[0] = 0x2c80 | (reg & 0xf);
dbg[1] = (data >> 16) & 0xffff;
dbg[2] = data & 0xffff;
dbg[3] = 0;
// Perform the wdebug instruction
#if 0
// This strain is for gas which doesn't have the wdebug instructions defined
asm( "move.l %0, %%a0\n\t"
".word 0xfbd0\n\t"
".word 0x0003\n\t"
:: "g" (dbg) : "a0");
#else
// And this is for when it does
asm( "wdebug (%0)" :: "a" (dbg));
#endif
}
#endif
Annotation
- Detected declarations: `function instructions`.
- Atlas domain: Architecture Layer / arch/m68k.
- 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.