fpu_xstate_prctl(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay so this is fpu_xstate_prctl from the Kernel API Manual, and the whole vibe is xstate permission operations ✨ literally the permission desk for xstate, bestie πŸ’…


✨ SYNOPSIS ✨

long fpu_xstate_prctl (int option , unsigned long arg2 );

πŸŽ€ ARGUMENTS πŸŽ€

  • option β€” a subfunction of arch_prctl 🫢
  • arg2 β€” the option argument, iykyk πŸ’–

πŸ’– RETURN πŸ’–

0 if successful; otherwise, an error code 😭 that’s the whole deal, no cap.


πŸ¦‹ DESCRIPTION πŸ¦‹

Option arguments, bestie β€” here’s the lineup πŸ‘‘

  • ARCH_GET_XCOMP_SUPP β€” pointer to user space u64 to store the info ✨
  • ARCH_GET_XCOMP_PERM β€” pointer to user space u64 to store the info πŸ’–
  • ARCH_REQ_XCOMP_PERM β€” facility number requested πŸ‘‘

For facilities which require more than one XSTATE component, the request must be the highest state component number related to that facility, e.g. for AMX which requires XFEATURE_XTILE_CFG(17) and XFEATURE_XTILE_DATA(18) this would be XFEATURE_XTILE_DATA(18) πŸ”₯

fr fr, that β€œhighest component number” part is the main-character rule here β€” don’t show up with the lower one and expect it to slay πŸ’€

🌈 SEE ALSO 🌈


xoxo, your fave kernel bestie πŸ’… β€” source/version: ./arch/x86/kernel/fpu, date: October 2026, page: fpu_xstate_prctl(9) πŸŽ€

πŸ“¦ where this page comes from