vfio_pci_co...ersect_range(9)

💅 NAME 💅

vfio_pci_core_range_intersect_range — bestie, this one figures out whether a buffer and a register offset range are overlapping, and if they are, where and how much. Like a vibe check but for memory ranges. ✨

(This is from the Kernel API Manual, iykyk 🎀)

🌸 SYNOPSIS 🌸

bool vfio_pci_core_range_intersect_range(loff_t buf_start, size_t buf_cnt,
                                         loff_t reg_start, size_t reg_cnt,
                                         loff_t *buf_offset,
                                         size_t *intersect_count,
                                         size_t *register_offset);

🦋 ARGUMENTS 🦋

• buf_start — where the buffer starts, offset-wise. Main character energy for the buffer side 💖
• buf_cnt — how many bytes the buffer has. Like, its whole size, no cap.
• reg_start — the starting register offset. The other half of this little meet-cute 🫶
• reg_cnt — number of bytes in the register. Its size, periodt.
• buf_offset — output! Where the overlap kicks off inside the buffer. 👑
• intersect_count — output! How many bytes actually overlap. The number we've all been waiting for 💀
• register_offset — output! Where the overlap starts inside the register. Slay. 🌈

🔥 RETURN 🔥

true if there is overlap, false if there isn't — literally that simple, no crumbs. And when there is overlap, the start and size come back to you through the function args, which are those pointer params up there 💅

🧚 SEE ALSO 🧚

Kernel file ./drivers/vfio/pci/vfio_pci_config.c — go read it, bestie, it's giving source of truth 📖✨

Ok that's the whole page, you ate it up ngl 🍓

Alright that's it from ./drivers/vfio/pci, dated October 2026 — version vibes baked right in, mwah 💋🦋 See you in the kernel, bestie 💜