Function report

Linux Kernel

v5.5.9

Brick Technologies Co., Ltd

Source Code:arch\x86\kernel\fpu\init.c Create Date:2022-07-28 07:49:05
Last Modify:2020-03-12 14:18:49 Copyright©Brick
home page Tree
Annotation kernel can get tool activityDownload SCCTChinese

Name:Set up the user and kernel xstate sizes based on the legacy FPU context size.* We set this up first, and later it will be overwritten by* fpu__init_system_xstate() if the CPU knows about xstates.

Proto:static void __init fpu__init_system_xstate_size_legacy(void)

Type:void

Parameter:Nothing

196  on_boot_cpu((__section__(".init.data"))) = 1
198  WARN_ON_FPU(!on_boot_cpu)
199  on_boot_cpu = 0
206  If Not boot_cpu_has(Onboard FPU ) Then
207  Size of the FPU context state. All tasks in the system use the* same context size, regardless of what portion they use.* This is inherent to the XSAVE architecture which puts all state* components into a single, continuous memory block: = sizeof(structswregs_state)
208  Else
209  If boot_cpu_has(FXSAVE/FXRSTOR, CR4.OSFXSR ) Then Size of the FPU context state. All tasks in the system use the* same context size, regardless of what portion they use.* This is inherent to the XSAVE architecture which puts all state* components into a single, continuous memory block: = sizeof(structfxregs_state)
212  Else Size of the FPU context state. All tasks in the system use the* same context size, regardless of what portion they use.* This is inherent to the XSAVE architecture which puts all state* components into a single, continuous memory block: = sizeof(structfregs_state)
217  fpu_user_xstate_size = Size of the FPU context state. All tasks in the system use the* same context size, regardless of what portion they use.* This is inherent to the XSAVE architecture which puts all state* components into a single, continuous memory block:
Caller
NameDescribe
fpu__init_systemCalled on the boot CPU once per system bootup, to set up the initial* FPU state that is later cloned into all processes: