summaryrefslogtreecommitdiff
path: root/softmmu
diff options
context:
space:
mode:
authorKashyap Chamarthy <kchamart@redhat.com>2020-02-25 17:56:18 +0100
committerPaolo Bonzini <pbonzini@redhat.com>2020-03-16 23:02:25 +0100
commit3b2c52c017fa74783435bc1a429a96ae5e5b164b (patch)
tree36f524a40a0014685a5d1d0b2b9bf9c0f66ba6b1 /softmmu
parent76c51fc3af34a02a5b6ecebe87dc2c2830251d16 (diff)
downloadqemu-3b2c52c017fa74783435bc1a429a96ae5e5b164b.zip
qemu-cpu-models.rst: Document -noTSX, mds-no, taa-no, and tsx-ctrl
- Add the '-noTSX' variants for CascadeLake and SkyLake. - Document the three MSR bits: 'mds-no', 'taa-no', and 'tsx-ctrl' Two confusing things about 'mds-no' (and the first point applies to the other two MSRs too): (1) The 'mds-no' bit will _not_ show up in the guest's /proc/cpuinfo. Rather it is used to fill in the guest's sysfs: /sys/devices/system/cpu/vulnerabilities/mds:Not affected Paolo confirmed on IRC as such. (2) There are _three_ variants[+] of CascadeLake CPUs, with different stepping levels: 5, 6, and 7. To quote wikichip.org[*]: "note that while steppings 6 & 7 are fully mitigated, earlier stepping 5 is not protected against MSBDS, MLPDS, nor MDSUM" The above is also indicated in the Intel's document[+], as indicated by "No" under the three columns of MFBDS, MSBDS, and MLPDS. I've expressed this in the docs without belabouring the details. [+] https://software.intel.com/security-software-guidance/insights/processors-affected-microarchitectural-data-sampling [*] https://en.wikichip.org/wiki/intel/microarchitectures/cascade_lake#Key_changes_from_Skylake Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com> Message-Id: <20200225165618.6571-3-kchamart@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'softmmu')
0 files changed, 0 insertions, 0 deletions