xe_reg_white..._print_entry(9)

💅 xe_reg_white..._print_entry(9) — from the Kernel API Manual, bestie 🎀

okay so picture this: you're deep in the kernel manual (yes, that one), and you stumble on xe_reg_whitelist_print_entry. It's giving "small function, big responsibilities." Let's get into it ✨

---

✨ NAME ✨

xe_reg_whitelist_print_entry — the little function whose whole entire job is printing one whitelist entry. That's it. That's the gig. 💖

---

🦋 SYNOPSIS 🦋

void xe_reg_whitelist_print_entry (struct drm_printer *p , unsigned int
indent , u32 reg , struct xe_reg_sr_entry *entry );

no cap, that's the whole signature. copy it exactly, don't be out here renaming things 🙈

---

🌸 ARGUMENTS 🌸

• p — the DRM printer 🖨️ like, the thing that actually does the printing. main character energy.
• indent — the indent level 🌈 so your output looks cute and nested instead of chaotic.
• reg — the register that's allowed/denied 👑 yes, both. it's flexible like that.
• entry — the save-restore entry 💾 the actual data being shown off.

---

💜 DESCRIPTION 💜

It prints the deets about the entry that got added to allow/deny access. literally that's the vibe — one entry, one print, details included. bestie it's not complicated and that's what makes it iconic 💅

---

🔥 SEE ALSO 🔥

• Kernel file ./drivers/gpu/drm/xe/xe_reg_whitelist.c — go read the source, iykyk 📂
• xe_reg_whitelist_process_engine(9) 🚀
• xe_reg_whitelist_oa_regs(9) 🎯
• xe_reg_dewhitelist_oa_regs(9) 💀 (yes, "dewhitelist" is a real word here)
• xe_reg_whitelist_dump(9) 🗑️✨

---

go off and print those entries, bestie 🫶 but fr fr, keep the arguments exactly as written — no guessing, no "fixing", no inventing flags that don't exist. we stay factual in this group chat 💖

---

and that's the page!! brought to you by ./drivers/gpu/drm/xe, dated October 2026, page name xe_reg_white..._print_entry(9) ⭐ slay, bye 🧚💜