STRUCT DC_PROBE_STATUS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct dc_probe_status(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual entry for struct dc_probe_status β€” literally the lil result basket for a probe. no cap, this one is short but every field matters, so let’s get into it πŸ’–


🌸 NAME 🌸

struct dc_probe_status β€” results for a probe.

✨ SYNOPSIS ✨

       struct dc_probe_status {
           bool valid;
           enum dc_probe_type         type;
           union {
             uint32_t bandwidth_mbps;
             struct dc_probe_latencies latency;
             uint32_t urgent_assertion_count;
             uint32_t prefetch_data_size;
           } u;
        };

🫢 Members 🫢

  • valid β€” true if a measurement was latched. like, the vibe check passed and a value actually got locked in ✨
  • type β€” type of the probe that produced this result. this tells you which probe said β€œhey, here’s your data” πŸ‘‘
  • u.bandwidth_mbps β€” peak BW in Mbps (DC_PROBE_PEAK_MEM_BW). bandwidth girlie reporting for duty πŸ”₯
  • u.latency β€” min/max/avg memory latency in ns (DC_PROBE_MEM_LATENCY), stored as struct dc_probe_latencies. the full latency trio, iconic 😭
  • u.urgent_assertion_count β€” number of urgent assertion events (DC_PROBE_URGENT_ASSERTION_COUNT). counting the urgent moments fr fr πŸ’€
  • u.prefetch_data_size β€” total prefetch data in bytes (DC_PROBE_PREFETCH_DATA_SIZE). all the prefetch bytes, summed up πŸŽ€

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/gpu/drm/amd/display/dc/dc.h:


and that’s the whole page, bestie πŸ¦‹ huge shoutout to the source path ./drivers/gpu/drm/amd/display/dc and the date October 2026 β€” this has been struct dc_probe_status(9), byeee πŸ’–

πŸ“¦ where this page comes from