linux-toradex.git/arch/powerpc/include/asm/kvm_fpu.h, branch v3.3.1 Linux kernel for Apalis and Colibri modules powerpc: Remove fpscr use from [kvm_]cvt_{fd,df} 2010-09-02T04:07:32+00:00 Andreas Schwab schwab@linux-m68k.org 2010-08-21T11:43:20+00:00 05d77ac90c0d260ae18decd70507dc4f5b71a2cb Neither lfs nor stfs touch the fpscr, so remove the restore/save of it around them. Signed-off-by: Andreas Schwab <schwab@linux-m68k.org> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org> 
Neither lfs nor stfs touch the fpscr, so remove the restore/save of it
around them.

Signed-off-by: Andreas Schwab <schwab@linux-m68k.org>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
KVM: PPC: elide struct thread_struct instances from stack 2010-08-01T07:39:24+00:00 Andreas Schwab schwab@linux-m68k.org 2010-05-31T19:59:13+00:00 49f6be8ea1bd74713c1a48e42db06a3808dfa2cd Instead of instantiating a whole thread_struct on the stack use only the required parts of it. Signed-off-by: Andreas Schwab <schwab@linux-m68k.org> Tested-by: Alexander Graf <agraf@suse.de> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com> 
Instead of instantiating a whole thread_struct on the stack use only the
required parts of it.

Signed-off-by: Andreas Schwab <schwab@linux-m68k.org>
Tested-by: Alexander Graf <agraf@suse.de>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
KVM: PPC: Add helpers to call FPU instructions 2010-04-25T09:35:15+00:00 Alexander Graf agraf@suse.de 2010-02-19T10:00:40+00:00 963cf3dc6342fe60bb78c615884537621abca0bc To emulate paired single instructions, we need to be able to call FPU operations from within the kernel. Since we don't want gcc to spill arbitrary FPU code everywhere, we tell it to use a soft fpu. Since we know we can really call the FPU in safe areas, let's also add some calls that we can later use to actually execute real world FPU operations on the host's FPU. Signed-off-by: Alexander Graf <agraf@suse.de> Signed-off-by: Avi Kivity <avi@redhat.com> 
To emulate paired single instructions, we need to be able to call FPU
operations from within the kernel. Since we don't want gcc to spill
arbitrary FPU code everywhere, we tell it to use a soft fpu.

Since we know we can really call the FPU in safe areas, let's also add
some calls that we can later use to actually execute real world FPU
operations on the host's FPU.

Signed-off-by: Alexander Graf <agraf@suse.de>
Signed-off-by: Avi Kivity <avi@redhat.com>