afu_dma_region_find_iova(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– afu_dma_region_find_iova(9) β€” like, the whole entire vibe πŸ’–

okay so bestie, welcome to the Kernel API Manual ✨ pull up a chair, grab a boba, because we're about to talk about finding a DMA region in an rbtree and honestly? it's giving main character energy πŸŽ€


🌸 NAME 🌸

afu_dma_region_find_iova β€” ok so what it DOES is it finds the dma region from rbtree by iova πŸ¦‹ that's literally it, that's the whole job, and it does it slayfully


✨ SYNOPSIS ✨

struct dfl_afu_dma_region * afu_dma_region_find_iova (struct
dfl_feature_dev_data *fdata , u64 iova );

like, you hand it your feature dev data and an iova, and it hands you back a struct dfl_afu_dma_region * 🫢 no cap


πŸ’… ARGUMENTS πŸ’…

  • fdata β€” the feature dev data πŸ’– that's your context, your whole situation
  • iova β€” the address of the dma region 🌸 (a u64, in case you were wondering, and yes it's in the synopsis too, i'm just being thorough)

πŸ”₯ DESCRIPTION πŸ”₯

okay so here's the thing that actually matters, and i need you to hear me on this one:

Needs to be called with fdata->lock held. πŸ”’

like. held. as in you already grabbed the lock before you call this, bestie 😭 this function is NOT gonna do it for you, it's not that kind of function, it's a you do the locking kind of function. so lock it up first, then call, okay? periodt πŸ’€


🌈 SEE ALSO 🌈

the kernel file is ./drivers/fpga/dfl-afu-dma-region.c β€” go read it, it's iconic πŸ‘‘

and then the whole friend group of related functions, all of which you can and should look up:


and that's the page, bestie πŸ’œ shoutout to ./drivers/fpga for being the source and the whole October 2026 situation for the date β€” like she's from the future, we respect it πŸ§šβ€β™€οΈβ­ bye!! πŸ“

πŸ“¦ where this page comes from