diff options
author | David Gibson <david@gibson.dropbear.id.au> | 2011-10-10 18:31:01 +0000 |
---|---|---|
committer | Alexander Graf <agraf@suse.de> | 2011-10-30 17:11:53 +0100 |
commit | 6659394fa1fa20aa640efa42c8fa5ee6994b6286 (patch) | |
tree | ff22a1243e72494798b10a61b9464a836c63920a /hw/pxa2xx_lcd.c | |
parent | 9bc884b741d3ab5bc3471a5cbccc38480676bf2b (diff) | |
download | qemu-6659394fa1fa20aa640efa42c8fa5ee6994b6286.tar.gz qemu-6659394fa1fa20aa640efa42c8fa5ee6994b6286.tar.bz2 qemu-6659394fa1fa20aa640efa42c8fa5ee6994b6286.zip |
pseries: Add device tree properties for VMX/VSX and DFP under kvm
Sufficiently recent PAPR specifications define properties "ibm,vmx"
and "ibm,dfp" on the CPU node which advertise whether the VMX vector
extensions (or the later VSX version) and/or the Decimal Floating
Point operations from IBM's recent POWER CPUs are available.
Currently we do not put these in the guest device tree and the guest
kernel will consequently assume they are not available. This is good,
because they are not supported under TCG. VMX is similar enough to
Altivec that it might be trivial to support, but VSX and DFP would
both require significant work to support in TCG.
However, when running under kvm on a host which supports these
instructions, there's no reason not to let the guest use them. This
patch, therefore, checks for the relevant support on the host CPU
and, if present, advertises them to the guest as well.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Alexander Graf <agraf@suse.de>
Diffstat (limited to 'hw/pxa2xx_lcd.c')
0 files changed, 0 insertions, 0 deletions