aboutsummaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-gemini/Makefile.boot
diff options
context:
space:
mode:
authorRussell King <rmk+kernel@arm.linux.org.uk>2010-02-06 06:27:45 -0500
committerRussell King <rmk+kernel@arm.linux.org.uk>2010-02-15 16:39:53 -0500
commit54cb3dbb4a1cccd6b1bffc169ff638f8e74daf44 (patch)
tree454b05810dc96b288eabcc4e11046adb0bc8b8ec /arch/arm/mach-gemini/Makefile.boot
parent462f39a8c7496c95f4de91ef46d875f46e0fa271 (diff)
ARM: vfp: fix vfp_sync_state()
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>
Diffstat (limited to 'arch/arm/mach-gemini/Makefile.boot')
0 files changed, 0 insertions, 0 deletions