debug_evictions(bool)(9)

💅 debug_evictions(bool) 💅

ok so bestie, we're in the Kernel API Manual today and this one is short but she is mighty. grab your lil strawberry drink 🍓 and let's go.

✨ DESCRIPTION ✨

So what does this icon actually do? Literally one job, and she ate:

Enable extra debug messages to help determine the cause of evictions

That's it. That's the whole personality. You turn on debug_evictions (it's a bool, so it's a yes/no vibe check 🎀) and the kernel gets chatty about why things are getting evicted. Not me explaining evictions in depth though, because the page doesn't, and I'm not about to invent lore. no cap. 💀

Think of it as: the kernel putting on her reading glasses and telling you what's going on instead of just silently yeeting stuff. iconic behavior, honestly. 👑

🌈 SEE ALSO 🌈

ok this is the part where the page goes absolutely FERAL — there are like a hundred sibling parameters and I'm listing every single one, unchanged, because I love you and I refuse to drop a single crumb 🫶✨

The family lives in the kernel file ./drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c:

vramlimit (int)(9), vis_vramlimit (int)(9), gartsize (uint)(9), gttsize (int)(9),
moverate (int)(9), audio (int)(9), disp_priority (int)(9), hw_i2c
(int)(9), pcie_gen2 (int)(9), msi (int)(9), svm_default_granularity
(uint)(9), lockup_timeout (string)(9), dpm (int)(9), fw_load_type
(int)(9), aspm (int)(9), runpm (int)(9), ip_block_mask (uint)(9), bapm
(int)(9), deep_color (int)(9), vm_size (int)(9), vm_fragment_size
(int)(9), vm_block_size (int)(9), vm_fault_stop (int)(9), vm_update_mode
(int)(9), exp_hw_support (int)(9), dc (int)(9), sched_jobs (int)(9),
sched_hw_submission (int)(9), ppfeaturemask (hexint)(9),
forcelongtraining (uint)(9), pcie_gen_cap (uint)(9), pcie_lane_cap
(uint)(9), cg_mask (ullong)(9), pg_mask (uint)(9), sdma_phase_quantum
(uint)(9), disable_cu (charp)(9), virtual_display (charp)(9), lbpw
(int)(9), gpu_recovery (int)(9), emu_mode (int)(9), ras_enable (int)(9),
ras_mask (uint)(9), timeout_fatal_disable (bool)(9), timeout_period
(uint)(9), si_support (int)(9), cik_support (int)(9),
smu_memory_pool_size (uint)(9), async_gfx_ring (int)(9), mcbp (int)(9),
discovery (int)(9), mes_log_enable (int)(9), uni_mes (int)(9), noretry
(int)(9), force_asic_type (int)(9), use_xgmi_p2p (int)(9), sched_policy
(int)(9), hws_max_conc_proc (int)(9), cwsr_enable (int)(9),
max_num_of_queues_per_device (int)(9), send_sigterm (int)(9),
halt_if_hws_hang (int)(9), hws_gws_support(bool)(9),
queue_preemption_timeout_ms (int)(9), no_system_mem_limit(bool)(9),
no_queue_eviction_on_vm_fault (int)(9), mtype_local (int)(9), pcie_p2p
(bool)(9), dcfeaturemask (uint)(9), dcdebugmask (uint)(9), abmlevel
(uint)(9), damageclips (int)(9), tmz (int)(9), freesync_video (uint)(9),
reset_method (int)(9), bad_page_threshold (int) Bad page threshold is
specifies the(9), vcnfw_log (int)(9), sg_display (int)(9), umsch_mm
(int)(9), umsch_mm_fwlog (int)(9), smu_pptable_id (int)(9),
partition_mode (int)(9), enforce_isolation (int)(9), modeset (int)(9),
seamless (int)(9), debug_mask (uint)(9), agp (int)(9), wbrf (int)(9),
rebar (int)(9), user_queue (int)(9), ptl (int)(9)

yes, bad_page_threshold (int) Bad page threshold is specifies the(9) really does say that in the source page. I did not do this. I am simply the messenger and I am holding it up like a proud mom. 😭💀 Reproduced exactly, typos and all, because that's the assignment and I don't fumble the bag.

Also bestie, note that a bunch of these have different types in their parens — int, uint, hexint, ullong, string, charp, bool — and I kept every single one exactly as written. no merging, no "fixing". iykyk 🧚

and that's the whole page!! tiny page, huge SEE ALSO energy. 🌸

this lil masterpiece comes to you from ./drivers/gpu/drm/amd/amdgpu, dated October 2026 — mwah, love that for us 💜🦋 periodt