libvirt/tests/cputestdata/x86_64-cpuid-Core2-E6850-guest.xml

<cpu mode='custom' match='exact'>
  <model fallback='forbid'>Conroe</model>
  <vendor>Intel</vendor>
  <feature policy='require' name='vme'/>
  <feature policy='require' name='ds'/>
  <feature policy='require' name='acpi'/>
  <feature policy='require' name='ss'/>
  <feature policy='require' name='ht'/>
  <feature policy='require' name='tm'/>
  <feature policy='require' name='pbe'/>
  <feature policy='require' name='dtes64'/>
  <feature policy='require' name='monitor'/>
  <feature policy='require' name='ds_cpl'/>
  <feature policy='require' name='vmx'/>
  <feature policy='require' name='smx'/>
  <feature policy='require' name='est'/>
  <feature policy='require' name='tm2'/>
  <feature policy='require' name='cx16'/>
  <feature policy='require' name='xtpr'/>
  <feature policy='require' name='pdcm'/>
</cpu>
tests: Add CPU detection test for Intel Core2 Duo E6850 Signed-off-by: Jiri Denemark <jdenemar@redhat.com> 2016-06-01 18:52:53 +03:00			`<cpu mode='custom' match='exact'>`
cpu_x86: Use signature in CPU detection code Our current detection code uses just the number of CPU features which need to be added/removed from the CPU model to fully describe the CPUID data. The smallest number wins. But this may sometimes generate wrong results as one can see from the fixed test cases. This patch modifies the algorithm to prefer the CPU model with matching signature even if this model results in a longer list of additional features. Signed-off-by: Jiri Denemark <jdenemar@redhat.com> 2015-06-25 16:06:19 +03:00			`<model fallback='forbid'>Conroe</model>`
tests: Add CPU detection test for Intel Core2 Duo E6850 Signed-off-by: Jiri Denemark <jdenemar@redhat.com> 2016-06-01 18:52:53 +03:00			`<vendor>Intel</vendor>`
cpu_x86: Use signature in CPU detection code Our current detection code uses just the number of CPU features which need to be added/removed from the CPU model to fully describe the CPUID data. The smallest number wins. But this may sometimes generate wrong results as one can see from the fixed test cases. This patch modifies the algorithm to prefer the CPU model with matching signature even if this model results in a longer list of additional features. Signed-off-by: Jiri Denemark <jdenemar@redhat.com> 2015-06-25 16:06:19 +03:00			`<feature policy='require' name='vme'/>`
tests: Add CPU detection test for Intel Core2 Duo E6850 Signed-off-by: Jiri Denemark <jdenemar@redhat.com> 2016-06-01 18:52:53 +03:00			`<feature policy='require' name='ds'/>`
			`<feature policy='require' name='acpi'/>`
			`<feature policy='require' name='ss'/>`
			`<feature policy='require' name='ht'/>`
			`<feature policy='require' name='tm'/>`
			`<feature policy='require' name='pbe'/>`
			`<feature policy='require' name='dtes64'/>`
cpu_x86: Use signature in CPU detection code Our current detection code uses just the number of CPU features which need to be added/removed from the CPU model to fully describe the CPUID data. The smallest number wins. But this may sometimes generate wrong results as one can see from the fixed test cases. This patch modifies the algorithm to prefer the CPU model with matching signature even if this model results in a longer list of additional features. Signed-off-by: Jiri Denemark <jdenemar@redhat.com> 2015-06-25 16:06:19 +03:00			`<feature policy='require' name='monitor'/>`
tests: Add CPU detection test for Intel Core2 Duo E6850 Signed-off-by: Jiri Denemark <jdenemar@redhat.com> 2016-06-01 18:52:53 +03:00			`<feature policy='require' name='ds_cpl'/>`
			`<feature policy='require' name='vmx'/>`
			`<feature policy='require' name='smx'/>`
			`<feature policy='require' name='est'/>`
			`<feature policy='require' name='tm2'/>`
			`<feature policy='require' name='cx16'/>`
			`<feature policy='require' name='xtpr'/>`
			`<feature policy='require' name='pdcm'/>`
			`</cpu>`