libvirt/tests/cputestdata/x86-host-Haswell-noTSX+Haswell,haswell,Haswell-result.xml

<cpu mode='custom' match='exact'>
  <arch>x86_64</arch>
  <model fallback='allow'>Haswell</model>
  <feature policy='disable' name='hle'/>
  <feature policy='disable' name='rtm'/>
</cpu>
cpu: Add {Haswell,Broadwell}-noTSX CPU models QEMU 2.3 adds these new models to cover Haswell and Broadwell CPUs with updated microcode. Luckily, they also reverted former the machine type specific changes to existing models. And since these changes were never released, we don't need to hack around them in libvirt. Signed-off-by: Jiri Denemark <jdenemar@redhat.com> 2015-03-23 16:19:28 +00:00			`<cpu mode='custom' match='exact'>`
			`<arch>x86_64</arch>`
			`<model fallback='allow'>Haswell</model>`
			`<feature policy='disable' name='hle'/>`
cpu_x86: Use array of features in CPU map There's no reason for keeping the features in a linked list. Especially when we know upfront the total number of features we are loading. Signed-off-by: Jiri Denemark <jdenemar@redhat.com> 2016-05-17 13:15:40 +00:00			`<feature policy='disable' name='rtm'/>`
cpu: Add {Haswell,Broadwell}-noTSX CPU models QEMU 2.3 adds these new models to cover Haswell and Broadwell CPUs with updated microcode. Luckily, they also reverted former the machine type specific changes to existing models. And since these changes were never released, we don't need to hack around them in libvirt. Signed-off-by: Jiri Denemark <jdenemar@redhat.com> 2015-03-23 16:19:28 +00:00			`</cpu>`