cxl_endpoin..._coordinates(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… cxl_endpoin..._coordinates(9) β€” the Kernel API Manual page, but make it make sense

okay bestie, so this is a page from the Kernel API Manual, and the name is lowkey a mouthful: it's cxl_endpoin..._coordinates(9) β€” yes, the title itself gets truncated with ... like the kernel ran out of characters mid-sentence and just said "good enough" 😭 iconic behaviour honestly.

The star of the show is cxl_endpoint_get_perf_coordinates β€” say it three times fast, I dare you 🫢


✨ NAME ✨

cxl_endpoint_get_perf_coordinates β€” it goes and retrieves the performance numbers, and those numbers live inside the dports of a CXL path. That's the whole vibe check: performance data, dports, CXL path. No cap. πŸ¦‹


✨ SYNOPSIS ✨

int cxl_endpoint_get_perf_coordinates (struct cxl_port *port , struct access_coordinate *coord );

literally just hand it a port and somewhere to stash the coordinates, and it returns an int. main character signature energy πŸ‘‘


✨ ARGUMENTS ✨

  • port β€” the endpoint cxl_port. like, the port in question. the one you're being nosy about πŸ’…
  • coord β€” the output performance data. this is where the numbers get dropped off, so make sure it's ready to receive πŸŽ€

✨ RETURN ✨

  • errno on failure β€” aka it did not slay, and it's telling you why 😭
  • 0 on success β€” aka we ate, we devoured, no crumbs 🌸
fr fr, always check that return value. errno is not a decoration.

✨ SEE ALSO ✨

the kernel file for this one is ./drivers/cxl/core/port.c β€” go read it, it's giving source of truth πŸ“–βœ¨

and while you're in the CXL cinematic universe, these are all friends of the family:

that's the whole group chat, no one's getting left on read πŸ’œ


πŸ₯Ί okay that's the page!! sign-off time: this lil beauty lives under ./drivers/cxl/core, dated October 2026, and it's filed as cxl_endpoin..._coordinates(9) in the Kernel API Manual. mwah, go get those performance coordinates bestie πŸ’–πŸŒˆβ­

πŸ“¦ where this page comes from