diff options
author | Mihai Caraman <mihai.caraman@freescale.com> | 2014-08-20 16:36:23 +0300 |
---|---|---|
committer | Alexander Graf <agraf@suse.de> | 2014-09-22 10:11:32 +0200 |
commit | 95d80a294b1eec83eb58c57e101b05828d97a851 (patch) | |
tree | ba3cd2f22c938638926ee4fff629d594f8c79b2d /arch/mn10300 | |
parent | 3efc7da61f6c5af78f67f03df8b0e1a473d8bc45 (diff) | |
download | op-kernel-dev-95d80a294b1eec83eb58c57e101b05828d97a851.zip op-kernel-dev-95d80a294b1eec83eb58c57e101b05828d97a851.tar.gz |
KVM: PPC: Book3e: Add AltiVec support
Add AltiVec support in KVM for Book3e. FPU support gracefully reuse host
infrastructure so follow the same approach for AltiVec.
Book3e specification defines shared interrupt numbers for SPE and AltiVec
units. Still SPE is present in e200/e500v2 cores while AltiVec is present in
e6500 core. So we can currently decide at compile-time which of the SPE or
AltiVec units to support exclusively by using CONFIG_SPE_POSSIBLE and
CONFIG_PPC_E500MC defines. As Alexander Graf suggested, keep SPE and AltiVec
exception handlers distinct to improve code readability.
Guests have the privilege to enable AltiVec, so we always need to support
AltiVec in KVM and implicitly in host to reflect interrupts and to save/restore
the unit context. KVM will be loaded on cores with AltiVec unit only if
CONFIG_ALTIVEC is defined. Use this define to guard KVM AltiVec logic.
Signed-off-by: Mihai Caraman <mihai.caraman@freescale.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
Diffstat (limited to 'arch/mn10300')
0 files changed, 0 insertions, 0 deletions