walk_iomem_res_desc(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– walk_iomem_res_desc(9) β€” Kernel API Manual πŸ’–

okay bestie, you're reading the walk_iomem_res_desc(9) page from the Kernel API Manual, and it's giving resource-walk realness ✨ let's go.


🌸 NAME 🌸

walk_iomem_res_desc β€” takes a little stroll through iomem resources and calls func() for the matching resource ranges. *

(yes, that trailing * is literally part of the NAME line β€” details are the moment πŸ’…)


✨ SYNOPSIS ✨

int walk_iomem_res_desc (unsigned long desc , unsigned long flags , u64
start , u64 end , void *arg , int (*func)(struct resource *, void *) );

πŸŽ€ ARGUMENTS πŸŽ€

  • desc β€” the I/O resource descriptor. Pass IORES_DESC_NONE if you want to skip the desc check entirely, bestie πŸ’–
  • flags β€” the I/O resource flags.
  • start β€” start addr.
  • end β€” end addr.
  • arg β€” the function argument that gets handed to the callback func.
  • func β€” the callback function; it gets called for each qualifying resource area.

πŸ¦‹ DESCRIPTION πŸ¦‹

So the valid candidates are all the memory ranges that overlap start,end and also match both flags and desc. That's the whole vibe check: overlap + matching flags + matching desc = candidate πŸ¦‹πŸ’–


πŸ’… NOTE πŸ’…

For a new descriptor search, define a new IORES_DESC in <linux/ioport.h> and set it in 'desc' of a target resource entry. That's the move πŸ‘‘


πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./kernel/resource.c β€” and then the whole resource-friend group chat:


okay that's the page, bestie πŸ’‹ source/version: ./kernel; date: October 2026. walk_iomem_res_desc(9) out β€” slay responsibly 🫢

πŸ“¦ where this page comes from