ntb_msg_read_sts(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

okay so this is ntb_msg_read_sts β€” it reads the message registers status, bestie ✨ (and yes, the manual we're chilling in is the Kernel API Manual, section 9, iykyk πŸ’…)


πŸ¦‹ SYNOPSIS πŸ¦‹

u64 ntb_msg_read_sts (struct ntb_dev *ntb );

πŸŽ€ ARGUMENTS πŸŽ€

  • ntb β€” the NTB device context, aka the whole vibe of the hardware you're talking to 🫢

🌸 DESCRIPTION 🌸

okay so picture this: you wanna know the status of the message register, right? that's literally the whole job. this function reads it. main character energy, no cap πŸ‘‘

and here's the cute part β€” the inbound bits and the outbound bits of the message registers can both be filtered by masks that you go get from ntb_msg_inbits and ntb_msg_outbits. so you grab your masks, you filter your bits, you slay πŸ’…


⭐ RETURN ⭐

it hands you back the status bits of the message registers, periodt πŸ”₯


πŸ‘‘ SEE ALSO πŸ‘‘

the kernel file ./include/linux/ntb.h is where it all lives, and here's the full friend group β€” every single one, fr fr:

enum ntb_topo(9), enum ntb_speed(9), enum ntb_width(9), enum ntb_default_port(9), struct ntb_client_ops(9), struct ntb_ctx_ops(9), struct ntb_dev_ops(9), struct ntb_client(9), struct ntb_dev(9), ntb_register_client(9), ntb_unregister_client(9), ntb_register_device(9), ntb_unregister_device(9), ntb_set_ctx(9), ntb_clear_ctx(9), ntb_link_event(9), ntb_db_event(9), ntb_msg_event(9), ntb_default_port_number(9), ntb_default_peer_port_count(9), ntb_default_peer_port_number(9), ntb_default_peer_port_idx(9), ntb_port_number(9), ntb_peer_port_count(9), ntb_peer_port_number(9), ntb_logical_port_number(9), ntb_peer_logical_port_number(9), ntb_peer_port_idx(9), ntb_link_is_up(9), ntb_link_enable(9), ntb_link_disable(9), ntb_mw_count(9), ntb_mw_get_align(9), ntb_mw_set_trans(9), ntb_mw_clear_trans(9), ntb_peer_mw_count(9), ntb_peer_mw_get_addr(9), ntb_peer_mw_set_trans(9), ntb_peer_mw_clear_trans(9), ntb_db_is_unsafe(9), ntb_db_valid_mask(9), ntb_db_vector_count(9), ntb_db_vector_mask(9), ntb_db_read(9), ntb_db_set(9), ntb_db_clear(9), ntb_db_read_mask(9), ntb_db_set_mask(9), ntb_db_clear_mask(9), ntb_peer_db_addr(9), ntb_peer_db_read(9), ntb_peer_db_set(9), ntb_peer_db_clear(9), ntb_peer_db_read_mask(9), ntb_peer_db_set_mask(9), ntb_peer_db_clear_mask(9), ntb_spad_is_unsafe(9), ntb_spad_count(9), ntb_spad_read(9), ntb_spad_write(9), ntb_peer_spad_addr(9), ntb_peer_spad_read(9), ntb_peer_spad_write(9), ntb_msg_count(9), ntb_msg_inbits(9), ntb_msg_outbits(9), ntb_msg_clear_sts(9), ntb_msg_set_mask(9), ntb_msg_clear_mask(9), ntb_msg_read(9), ntb_peer_msg_write(9), ntb_get_dma_dev(9), ntb_peer_resource_idx(9), ntb_peer_highest_mw_idx(9)


and that's the whole page, bestie πŸ§šπŸ’œ this lil gem comes from ./include/linux, dated October 2026, and it lives at ntb_msg_read_sts(9) β€” go read some message register status, you absolute icon πŸ“πŸŒˆ

πŸ“¦ where this page comes from