qm_invalid_queues(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… qm_invalid_queues β€” a kernel API manual moment

okay so bestie, welcome to qm_invalid_queues(9) from the Kernel API Manual πŸŽ€ this one's short and sweet but it's lowkey important, so let's get into it ✨


🌸 NAME 🌸

qm_invalid_queues β€” invalidates, like, all the queues currently in use. yes, all of them. every last one πŸ’€


πŸ¦‹ SYNOPSIS πŸ¦‹

void qm_invalid_queues (struct hisi_qm *qm );

πŸ’– ARGUMENTS πŸ’–

  • qm β€” the qm whose queues are about to get invalidated. that's the one we're doing this to, bestie 🫢

✨ DESCRIPTION ✨

so this function, right β€” it invalidates all queues in use. that's the whole vibe 🌈

and here's the tea β˜•: if the doorbell command gets sent to the device in user space after the device has been reset, the device just... discards that doorbell command. gone. not read. no cap πŸ™ˆ

fr fr, that's the actual documented behaviour β€” post-reset doorbells from user space get dropped by the device. don't come for me, that's just how it is πŸ’…

πŸ‘‘ SEE ALSO πŸ‘‘

the kernel file lives at ./drivers/crypto/hisilicon/qm.c and it's giving main character energy, so go read it. and then go read all of these too, because the whole squad is iconic:


🧚 sign-off 🧚

and that's the page!! source/version is ./drivers/crypto/hisilicon, dated October 2026, and the manpage name is ofc qm_invalid_queues(9) 🌸 go invalidate some queues responsibly bestie, ily, bye πŸ’œβœ¨

πŸ“¦ where this page comes from