fpu_xstate_prctl(9)
πΈ 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 ofarch_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 spaceu64to store the info β¨ARCH_GET_XCOMP_PERMβ pointer to user spaceu64to 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 π
- Kernel file
./arch/x86/kernel/fpu/xstate.cπ¦ check_xtile_data_against_struct(9)__copy_xstate_to_uabi_buf(9)copy_xstate_to_uabi_buf(9)copy_uabi_to_xstate(9)xsaves(9)xrstors(9)fpstate_realloc(9)
xoxo, your fave kernel bestie π
β source/version: ./arch/x86/kernel/fpu, date: October 2026, page: fpu_xstate_prctl(9) π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms