STRUCT AMDXDNA_DRM_GET_ARRAY(9)
π struct amdxdna_drm_get_array(9) β a lil' field guide
okay so this is from the Kernel API Manual, bestie, and it's literally the struct you use when you wanna get an information array out of the amdxdna driver. yeah. that's the whole vibe. let's get into it π«Ά
πΈ NAME πΈ
struct amdxdna_drm_get_array β Get information array. that's it, that's the tweet. she fetches info arrays, no cap π
β¨ SYNOPSIS β¨
here's the whole struct, character for character, do NOT touch her:
struct amdxdna_drm_get_array {
__u32 param;
__u32 element_size;
__u32 num_element;
__u32 pad;
__u64 buffer;
};
(yeah there's a lil' extra space before the closing brace in the original, we're keeping it, that's her little quirk π)
π¦ Members π¦
π param
the "what do you actually want, bestie" field. here's the supported lineup:
DRM_AMDXDNA_HW_CONTEXT_ALLβ returns all created hardware contexts. the whole friend group π₯DRM_AMDXDNA_HW_LAST_ASYNC_ERRβ returns the last async error. the receipts of what went wrong most recently πDRM_AMDXDNA_BO_USAGEβ returns usage of heap/internal/external BOs. she's nosy and she's counting π
πΈ element_size
specifies the maximum element sizeβ¦ and then comes back with the actual element size. so she takes a suggestion and gives you the truth. iconic behavior honestly π
β num_element
same energy: specifies the maximum number of elements, and returns the actual number of elements. she under-promises, she reports accurately π§
π pad
MBZ. and if you don't know what that means, it's "must be zero" β like, literally set it to zero, no cap, don't be weird about it π
π buffer
specifies the match conditions going in, returns the matched information array coming out. it's giving two-way street, it's giving bidirectional main character energy π¦
π SEE ALSO π
the kernel file where she actually lives: ./include/uapi/drm/amdxdna_accel.h
and her whole extended friend group, all of them, every last one, we don't leave a single mutual unmentioned:
struct amdxdna_drm_create_hwctx(9)struct amdxdna_drm_destroy_hwctx(9)struct amdxdna_cu_config(9)struct amdxdna_hwctx_param_config_cu(9)struct amdxdna_drm_config_hwctx(9)struct amdxdna_drm_va_entry(9)struct amdxdna_drm_va_tbl(9)struct amdxdna_drm_create_bo(9)struct amdxdna_drm_get_bo_info(9)struct amdxdna_drm_sync_bo(9)struct amdxdna_drm_exec_cmd(9)struct amdxdna_drm_wait_cmd(9)struct amdxdna_drm_query_aie_status(9)struct amdxdna_drm_query_aie_version(9)struct amdxdna_drm_query_aie_tile_metadata(9)struct amdxdna_drm_query_aie_metadata(9)struct amdxdna_drm_query_clock(9)struct amdxdna_drm_query_clock_metadata(9)struct amdxdna_drm_query_sensor(9)struct amdxdna_drm_query_hwctx(9)struct amdxdna_drm_get_power_mode(9)struct amdxdna_drm_query_firmware_version(9)struct amdxdna_drm_get_resource_info(9)struct amdxdna_drm_attribute_state(9)struct amdxdna_drm_query_telemetry_header(9)struct amdxdna_drm_get_info(9)struct amdxdna_drm_hwctx_entry(9)struct amdxdna_async_error(9)struct amdxdna_drm_bo_usage(9)struct amdxdna_drm_set_state(9)struct amdxdna_drm_set_power_mode(9)
k that's the whole page, mwah π this lil' slice of docs lives over in ./include/uapi/drm and it's dated October 2026 β so mark your calendars, hydrate, and remember: pad is MBZ, always πβ¨π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms