genwqe_health_thread(9)

🫶 genwqe_health_thread(9) 🫶

okay bestie, welcome to the Kernel API Manual entry for genwqe_health_thread — it’s giving “small thread, big responsibilities,” and we’re gonna get into all of it. no cap, every detail is staying. 💅

---

🎀 NAME 🎀

genwqe_health_thread — Health checking thread

✨ SYNOPSIS ✨

int genwqe_health_thread (void *data );

🦋 ARGUMENTS 🦋

• data — GenWQE device information

💅 DESCRIPTION 💅

okay so first thing: this thread is only started for the PF of the card. that’s the rule, bestie. ✨

This thread monitors the health of the card. A critical situation is when we read registers which contain -1 (IO_ILLEGAL_VALUE). In this case we need to be recovered from outside. Writing to registers will very likely not work either. 😭

This thread must only exit if kthread_should_stop becomes true. periodt.

Condition for the health-thread to trigger: a) when a kthread_stop request comes in or b) a critical GFIR occured. 🚨

Informational GFIRs are checked and potentially printed in GENWQE_HEALTH_CHECK_INTERVAL seconds.

🌈 SEE ALSO 🌈

Kernel file ./drivers/misc/genwqe/card_base.c — yes, that exact path, iconic.

• genwqe_devnode(9)
• genwqe_dev_alloc(9)
• genwqe_bus_reset(9)
• genwqe_recovery_on_fatal_gfir_required(9)
• genwqe_T_psec(9)
• genwqe_setup_pf_jtimer(9)
• genwqe_setup_vf_jtimer(9)
• genwqe_stop(9)
• genwqe_recover_card(9)
• genwqe_fir_checking(9)
• genwqe_pci_fundamental_reset(9)
• genwqe_reload_bistream(9)
• genwqe_pci_setup(9)
• genwqe_pci_remove(9)
• genwqe_probe(9)
• genwqe_remove(9)
• genwqe_err_error_detected(9)
• genwqe_init_module(9)
• genwqe_exit_module(9)

---

source/version: ./drivers/misc/genwqe · date: October 2026 — that’s the cute little sign-off, bestie, ty for reading, mwah 💋✨