microblaze_unwind_inner(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 microblaze_unwind_inner(9) 🌸

okay so bestie, welcome to the Kernel API Manual β€” this one's a kernel-level page for microblaze_unwind_inner(9), and it's literally the girlie that walks the stack for you. no cap, let's get into it 🫢


✨ NAME ✨

microblaze_unwind_inner β€” unwind the stack from the specified point πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

void microblaze_unwind_inner (struct task_struct *task , unsigned long
pc , unsigned long fp , unsigned long leaf_return , struct stack_trace
*trace , const char *loglvl );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • task β€” the task whose stack we're gonna unwind (it may be NULL, she's flexible like that πŸ™ˆ)
  • pc β€” the program counter where we start unwinding ✨
  • fp β€” the frame (stack) pointer where we start unwinding, the starting point of the whole vibe check πŸ“
  • leaf_return β€” the value of r15 at pc. if the function is a leaf, this is the caller's return address πŸ‘‘
  • trace β€” where to store the stack backtrace (the PC values). if it's NULL, that's the signal to print the backtrace to the kernel log instead πŸ–¨οΈ
  • loglvl β€” used for the printk log level if (trace == NULL). lowkey the volume knob for your logging πŸ’¬
⚠️ heads up bestie: task and trace both take NULL, but they mean different things β€” task = just no specific task, trace = print it to the kernel log instead of storing it. don't mix them up, iykyk πŸ’€

🌈 SEE ALSO 🌈

kernel file ./arch/microblaze/kernel/unwind.c, plus the whole friend group: get_frame_size(9), find_frame_creation(9), lookup_prev_stack_frame(9), unwind_trap(9), and microblaze_unwind(9) β€” they all ate, fr fr πŸ”₯


that's the whole page, periodt. πŸ’– this absolute icon comes to you from ./arch/microblaze/kernel, dated October 2026, and yes she's serving kernel API realness in microblaze_unwind_inner(9) form β€” go unwind some stacks babe, you got this β­πŸ§šβ€β™€οΈ

πŸ“¦ where this page comes from