alloc_test_workqueue_locked(9)

📦 version 7.3.1, in nixpkgs unstable

🧚 alloc_test_workqueue_locked(9) 💅

okay so buckle up bestie, this page comes straight out of the Kernel API Manual and it's honestly kind of a little baby function but it's so important, iykyk 🫶

✨ NAME ✨

alloc_test_workqueue_locked — a workqueue with its dworks and its mutex already initialised, like it came out of the box pre-glammed 💅

🎀 SYNOPSIS 🎀

struct hdcp_workqueue * alloc_test_workqueue_locked (struct kunit *test );

🌸 ARGUMENTS 🌸

  • test — the KUnit test context, which is doing the managed allocation for you so you don't have to think about cleanup (main character energy fr fr) ✨

🦋 DESCRIPTION 🦋

Okay so picture this: the function allocates a minimal hdcp_workqueue, and it doesn't just hand you a sad empty struct — no ma'am. It initialises the mutex and the three delayed works too, because that's literally the requirement for guard(mutex) and for process_output usage in the display update/remove/reset helpers. Like, the helpers need it to be ready-ready, and this gives you ready-ready. Slay. 💅

It's giving "small function, big responsibility" tbh 👑

💜 SEE ALSO 💜

okay this list is long long, so grab a snack 🍓 — every single one of these is in the kernel file ./drivers/gpu/drm/amd/display/amdgpu_dm/tests/amdgpu_dm_hdcp_test.c:

ngl that's a lot of cross-references and we listed every single one, no skipping, no summarizing, that's the whole point 💀✨

and that's the teaaaa 🫖 — this page is from the source ./drivers/gpu/drm/amd/display/... and it's dated October 2026, so like… future icon behaviour honestly 🌈⭐ bye bestie, go init a mutex 💖

📦 where this page comes from