Searched hist:"95 dd6974" (Results 1 – 1 of 1) sorted by relevance
/freebsd/sys/arm64/arm64/ |
H A D | exec_machdep.c | 95dd6974 Wed Jan 18 09:30:20 GMT 2023 Andrew Turner <andrew@FreeBSD.org> Always read the VFP regs in the arm64 fill_fpregs
The PCB_FP_STARTED is used to indicate that the current VFP context has been used since either 1. the start of the thread, or 2. exiting a kernel FP context.
When case 2 was added to the kernel this could cause incorrect results to be returned when a thread exits the kernel FP context and fill_fpregs is called before it has restored the VFP state, e.g. by trappin on a userspace VFP instruction.
In both of the cases the base save area is still valid so reduce the use of the PCB_FP_STARTED flag check to help decide if we need to store the current threads VFP state.
Sponsored by: Arm Ltd Differential Revision: https://reviews.freebsd.org/D37994 95dd6974 Wed Jan 18 09:30:20 GMT 2023 Andrew Turner <andrew@FreeBSD.org> Always read the VFP regs in the arm64 fill_fpregs
The PCB_FP_STARTED is used to indicate that the current VFP context has been used since either 1. the start of the thread, or 2. exiting a kernel FP context.
When case 2 was added to the kernel this could cause incorrect results to be returned when a thread exits the kernel FP context and fill_fpregs is called before it has restored the VFP state, e.g. by trappin on a userspace VFP instruction.
In both of the cases the base save area is still valid so reduce the use of the PCB_FP_STARTED flag check to help decide if we need to store the current threads VFP state.
Sponsored by: Arm Ltd Differential Revision: https://reviews.freebsd.org/D37994 95dd6974 Wed Jan 18 09:30:20 GMT 2023 Andrew Turner <andrew@FreeBSD.org> Always read the VFP regs in the arm64 fill_fpregs
The PCB_FP_STARTED is used to indicate that the current VFP context has been used since either 1. the start of the thread, or 2. exiting a kernel FP context.
When case 2 was added to the kernel this could cause incorrect results to be returned when a thread exits the kernel FP context and fill_fpregs is called before it has restored the VFP state, e.g. by trappin on a userspace VFP instruction.
In both of the cases the base save area is still valid so reduce the use of the PCB_FP_STARTED flag check to help decide if we need to store the current threads VFP state.
Sponsored by: Arm Ltd Differential Revision: https://reviews.freebsd.org/D37994 95dd6974 Wed Jan 18 09:30:20 GMT 2023 Andrew Turner <andrew@FreeBSD.org> Always read the VFP regs in the arm64 fill_fpregs
The PCB_FP_STARTED is used to indicate that the current VFP context has been used since either 1. the start of the thread, or 2. exiting a kernel FP context.
When case 2 was added to the kernel this could cause incorrect results to be returned when a thread exits the kernel FP context and fill_fpregs is called before it has restored the VFP state, e.g. by trappin on a userspace VFP instruction.
In both of the cases the base save area is still valid so reduce the use of the PCB_FP_STARTED flag check to help decide if we need to store the current threads VFP state.
Sponsored by: Arm Ltd Differential Revision: https://reviews.freebsd.org/D37994
|