forked from luck/tmp_suning_uos_patched
54cb3dbb4a
The more I look at vfp_sync_state(), the more I believe it's trying to do its job in a really obscure way. Essentially, last_VFP_context[] tracks who owns the state in the VFP hardware. If last_VFP_context[] is the context for the thread which we're interested in, then the VFP hardware has context which is not saved in the software state - so we need to bring the software state up to date. If last_VFP_context[] is for some other thread, we really don't care what state the VFP hardware is in; it doesn't contain any information pertinent to the thread we're trying to deal with - so don't touch the hardware. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> |
||
|---|---|---|
| .. | ||
| entry.S | ||
| Makefile | ||
| vfp.h | ||
| vfpdouble.c | ||
| vfphw.S | ||
| vfpinstr.h | ||
| vfpmodule.c | ||
| vfpsingle.c | ||