is_rcv_urgent_int(9)

💅 is_rcv_urgent_int(9) — like, the Kernel API Manual page you actually wanna read ✨

okay bestie, so this is is_rcv_urgent_int, straight out of the Kernel API Manual, and it's the handler for the urgent IRQ situation in the user receive context 🎀 ngl it's a tiny page but she's iconic in her own lowkey way.

---

✨ NAME ✨

is_rcv_urgent_int — the urgent IRQ handler for the user receive context 🫶

---

🌸 SYNOPSIS 🌸

void is_rcv_urgent_int (struct hfi1_devdata *dd , unsigned int source );

---

🦋 ARGUMENTS 🦋

• dd — a valid dd, yes ma'am, it has to be valid 💖
• source — the logical IRQ source, which is an offset from IS_RCVURGENT_START

---

👑 DESCRIPTION 👑

So the RX block gets a receive urgent interrupt, and this is the function that handles it 🔥 Easy. Also important: the source is < 160 — like, that's the rule, don't come at me with a 160 🫠

---

💀 NOTE 💀

Real talk: kernel receive contexts specifically do NOT enable this IRQ 🙈 Not a vibe, just a fact. That's literally what the note says, so don't @ me.

---

🎀 SEE ALSO 🎀

Kernel file ./drivers/infiniband/hw/hfi1/chip.c — go read her, she has lore 📖

Then the whole squad, and yes, I'm listing every single one of them because they all matter, periodt:

• hfi1_addr_from_offset(9)
• read_csr(9)
• write_csr(9)
• get_csr_addr(9)
• update_xmit_counters(9)
• apply_link_downgrade_policy(9)
• is_rcv_avail_int(9)
• general_interrupt(9)
• hfi1_rcd_eoi_intr(9)
• hfi1_netdev_rx_napi(9)
• data_vls_operational(9)
• encode_rcv_header_entry_size(9)
• hfi1_validate_rcvhdrcnt(9)
• set_hdrq_regs(9)
• update_statusp(9)
• wait_logical_linkstate(9)
• read_mod_write(9)
• set_intr_bits(9)
• set_up_interrupts(9)
• hfi1_get_qp_map(9)
• init_qpmap_table(9)
• init_qos(9)
• hfi1_init_dd(9)
• create_pbc(9)

---

fr fr that's the whole page — short, sweet, and extremely hfi1 coded 💜

and that's a wrap, bestie 🌈 this came from ./drivers/infiniband/hw/hfi1, dated October 2026 — mwah, slay, bye 💅✨