xe_vm_madvise_ioctl(9)

💖 xe_vm_madvise_ioctl(9) — Kernel API Manual, but make it cute 💖

Okay so bestie, welcome to the Kernel API Manual page for xe_vm_madvise_ioctl. This is lowkey the MADVise-ioctl handler for a VM, and we're gonna get into all of it, no cap.

🌸 NAME 🌸

xe_vm_madvise_ioctl — the handler for the MADVise ioctl on a VM. That's the whole name and the whole assignment, periodt.

🦋 SYNOPSIS 🦋

Here's the exact signature, copy-paste energy only:

int xe_vm_madvise_ioctl (struct drm_device *dev , void *data , struct
       drm_file *file );

🎀 ARGUMENTS 🎀

• dev — DRM device pointer. It's giving "which device are we even talking about?" energy.
• data — pointer to ioctl data, and that data is a drm_xe_madvise*. The asterisk is doing its little thing, iykyk.
• file — DRM file pointer. The DRM file bestie in question.

💜 DESCRIPTION 💜

So this function handles the MADVISE ioctl, and its whole job is to provide memory advice for vma's within input range. That's the vibe: memory advice, vma's, input range, iconic.

🔥 RETURN 🔥

• 0 on success.
• A negative error code on failure.

💀 SEE ALSO 💀

• Kernel file ./drivers/gpu/drm/xe/xe_vm_madvise.c
• struct xe_madvise_details(9)
• madvise_purgeable(9)
• madvise_range_needs_invalidation(9)

With love from the ./drivers/gpu/drm/xe corner of the source tree, stamped October 2026, on the xe_vm_madvise_ioctl(9) page. Read your man pages and hydrate, bestie 💅💖