| commit | 21ee4787e53367590f284915bf4c30c684e65bdf | |
| author | Daniel P. Berrangé <berrange@redhat.com> | |
| Thu, 7 Mar 2019 12:18:38 +0000 (7 12:18 +0000) | ||
| committer | Eduardo Habkost <ehabkost@redhat.com> | |
| Wed, 20 Mar 2019 15:18:15 +0000 (20 12:18 -0300) | ||
| tree | 04be0928158cbd1476c4a6453759af74932a7095 | treesnapshot (tar.gz zip) |
| parent | 174a78a8a5c0cf421236fe14efc5559717f050df | commitdiff |
docs: add note about stibp CPU feature for spectre v2
While the stibp CPU feature is not commonly used by guest OS for spectre
mitigation due to its performance impact, it is none the less best
practice to expose it to all guest OS. This allows the guest OS to
decide whether to make use or it.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Message-Id: <20190307121838.6345-3-berrange@redhat.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
While the stibp CPU feature is not commonly used by guest OS for spectre
mitigation due to its performance impact, it is none the less best
practice to expose it to all guest OS. This allows the guest OS to
decide whether to make use or it.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Message-Id: <20190307121838.6345-3-berrange@redhat.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
| docs/qemu-cpu-models.texi | diffblobblamehistory |