diff options
author | kib <kib@FreeBSD.org> | 2012-07-14 15:48:30 +0000 |
---|---|---|
committer | kib <kib@FreeBSD.org> | 2012-07-14 15:48:30 +0000 |
commit | 5bd2b3d73a52ccf1497165e4224696e551152035 (patch) | |
tree | aa9f4225bbf17a3b53982e7f3c810f1d7ab0ea28 /sys/amd64/include | |
parent | f9866864606d10b02b48047c44cc0d5d87003625 (diff) | |
download | FreeBSD-src-5bd2b3d73a52ccf1497165e4224696e551152035.zip FreeBSD-src-5bd2b3d73a52ccf1497165e4224696e551152035.tar.gz |
Add support for the XSAVEOPT instruction use. Our XSAVE/XRSTOR usage
mostly meets the guidelines set by the Intel SDM:
1. We use XRSTOR and XSAVE from the same CPL using the same linear
address for the store area
2. Contrary to the recommendations, we cannot zero the FPU save area
for a new thread, since fork semantic requires the copy of the
previous state. This advice seemingly contradicts to the advice
from the item 6.
3. We do use XSAVEOPT in the context switch code only, and the area
for XSAVEOPT already always contains the data saved by XSAVE.
4. We do not modify the save area between XRSTOR, when the area is
loaded into FPU context, and XSAVE. We always spit the fpu context
into save area and start emulation when directly writing into FPU
context.
5. We do not use segmented addressing to access save area, or rather,
always address it using %ds basing.
6. XSAVEOPT can be only executed in the area which was previously
loaded with XRSTOR, since context switch code checks for FPU use by
outgoing thread before saving, and thread which stopped emulation
forcibly get context loaded with XRSTOR.
7. The PCB cannot be paged out while FPU emulation is turned off, since
stack of the executing thread is never swapped out.
The context switch code is patched to issue XSAVEOPT instead of XSAVE
if supported. This approach eliminates one conditional in the context
switch code, which would be needed otherwise.
For user-visible machine context to have proper data, fpugetregs()
checks for unsaved extension blocks and manually copies pristine FPU
state into them, according to the description provided by CPUID leaf
0xd.
MFC after: 1 month
Diffstat (limited to 'sys/amd64/include')
-rw-r--r-- | sys/amd64/include/md_var.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/sys/amd64/include/md_var.h b/sys/amd64/include/md_var.h index ff11ea1..ff322bb 100644 --- a/sys/amd64/include/md_var.h +++ b/sys/amd64/include/md_var.h @@ -57,6 +57,7 @@ extern u_int cpu_procinfo; extern u_int cpu_procinfo2; extern char cpu_vendor[]; extern u_int cpu_vendor_id; +extern char ctx_switch_xsave[]; extern char kstack[]; extern char sigcode[]; extern int szsigcode; |