TABLE_SOC_UTM(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… TABLE_SOC_UTM(9) β€” the Kernel API Manual page, but make it make sense

okay so bestie, welcome to the TABLE_SOC_UTM(9) page β€” yeah it's a section 9 kernel API manual entry and honestly? it's kind of a baddie. let's get into it πŸ’–

✨ NAME ✨

TABLE_SOC_UTM β€” the SoC UTM QoS table. that's it, that's her. the table. the vibe. the QoS queen πŸ‘‘


πŸŽ€ SYNOPSIS πŸŽ€

TABLE_SOC_UTM

literally just her name, no arguments, no flags, no nothing. she's a table, not a whole CLI, bestie.


πŸ¦‹ DESCRIPTION πŸ¦‹

so what does she do? TABLE_SOC_UTM provides per-load-level bandwidth and latency bounds β€” which the display engine uses to meet its memory access requirements. think of it as the table that tells everyone how much memory bandwidth and how much latency each load level is allowed to have, and the display engine is like "thank u bestie, now i can hit my numbers" 🫢

there are two paths to get her in there:

  • Normal path 🌸 β€” she's embedded in DalInitTable_t, and gets fetched once via DALSMC_MSG_TransferTableSmu2Dram(TABLE_DAL_INIT).
  • Override path (debug only) ⚠️ β€” TABLE_SOC_UTM goes via DALSMC_MSG_TransferTableDram2Smu to override custom QoS parameters into PMFW.
bestie please note: that override path is debug only. don't be out here shipping custom QoS overrides into PMFW like it's a personality trait πŸ’€

πŸ‘‘ SEE ALSO πŸ‘‘

the kernel file in question, and like a lot of friends:


🌈 the cute sign-off 🌈

this page comes to you from ./drivers/gpu/drm/amd/display/..., dated October 2026, and it's filed under TABLE_SOC_UTM(9) πŸŽ€βœ¨ go read the other DALSMC_MSG pages, they ate too. periodt πŸ’œ

πŸ“¦ where this page comes from