kostikbel at gmail.com
Sun Jul 8 15:02:30 UTC 2012
Please find at
a patch to finally add suport for using XSAVEOPT for our amd64 context
switch code. See Intel SDM for description of the XSAVEOPT instruction.
Summary is that the instruction allows to not write parts of the FPU
state which was not touched by the thread. Context switch then would
write less to the PCB when thread is moved out from CPU. This is mainly
to facilitate the ever-growing size of the FPU register file, in
particular, AVX/YMM registers. Normal applications do not touch YMM, so
saving them on each context switch if FPU was used is waste.
Main complication is that any consumer of the ucontext_t still expect to
see fully populated machine state, including the extended states which were
not saved. Since CPU only avoids save when corresponding state is pristine,
we can use the copy of initial state. CPUID provides an enumerator that
allows OS to easily pick up neccesary area and copy over.
I tried hard, but was unable to measure any statistically significant
difference in the context switch times between XSAVE and XSAVEOPT using
lmbench lat_ctx, on Core i7 2600K.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-amd64/attachments/20120708/b020e58d/attachment.pgp
More information about the freebsd-amd64