tb_xdomain_alloc_in_hopid(9)

📦 version 7.3.1, in nixpkgs unstable

✨ tb_xdomain_alloc_in_hopid (9) — Kernel API Manual ✨

Okay so bestie, welcome to the Kernel API Manual, grab a lil snack 🍓 because we're about to talk about allocating an input HopID for tunneling. Yes, that's the NAME, and yes, it's exactly as iconic as it sounds 💅

🌈 SYNOPSIS

int tb_xdomain_alloc_in_hopid (struct tb_xdomain *xd , int hopid );

Literally that's the whole signature. Look at it. Gorgeous. No notes 🔥

🎀 ARGUMENTS

  • xd — the XDomain connection, your main character in this whole operation 💖
  • hopid — your preferred HopID, or you can pass -1 and let the kernel pick the next available one for you, king behaviour honestly 👑

🦋 DESCRIPTION

So here's the tea ☕: the HopID you get back is guaranteed to be within the range supported by the input lane adapter. Like, it's not gonna hand you something out of range, no cap. Fr fr.

And when you're done with it? You gotta call tb_xdomain_release_in_hopid to release the allocated HopID. Don't just leave it lying around, that's not the vibe 🙈

Bestie please remember the release call. Allocated resources don't clean themselves up, iykyk 💀

⭐ RETURN

  • Allocated HopID — on success 🎉 slay, you got one!
  • -ENOSPC — when there are literally no more available HopIDs left 😭 it's giving empty shelf energy
  • Negative errno — some other error happened, check the errno and see what's up 🫶

👑 SEE ALSO

Kernel file ./drivers/thunderbolt/xdomain.c, plus the whole friend group:

And that's the page, bestie! 🧚 This came out of ./drivers/thunderbolt and it's dated October 2026 — mwah, love that for us 💜💋

📦 where this page comes from