libvirt/tests/cputestdata/x86_64-cpuid-Xeon-E5-2623-v4-json.xml

<cpu mode='custom' match='exact'>
  <model fallback='forbid'>Broadwell-IBRS</model>
  <vendor>Intel</vendor>
  <feature policy='require' name='vme'/>
  <feature policy='require' name='ss'/>
  <feature policy='require' name='f16c'/>
  <feature policy='require' name='rdrand'/>
  <feature policy='require' name='hypervisor'/>
  <feature policy='require' name='arat'/>
  <feature policy='require' name='tsc_adjust'/>
  <feature policy='require' name='xsaveopt'/>
  <feature policy='require' name='pdpe1gb'/>
  <feature policy='require' name='abm'/>
</cpu>
cputest: Add data for Intel(R) Xeon(R) CPU E5-2623 v4 The CPU contains the updated microcode for CVE-2017-5715. The -guest.xml and -json.xml CPU definitions use Skylake-Client CPU model rather than Broadwell. This is similar to Xeon-E5-2650-v4 and it is caused by our CPU model selection code when no model matches the CPU signature (family + model). We'd need to maintain a complete list of CPU signatures for our CPU models to fix this. Signed-off-by: Jiri Denemark <jdenemar@redhat.com> Reviewed-by: Pavel Hrdina <phrdina@redhat.com> 2018-01-05 15:03:12 +01:00			`<cpu mode='custom' match='exact'>`
cpu_map: Add more signatures for Broadwell CPU models This fixes several CPUs which were incorrectly detected as Skylake-Client. Signed-off-by: Jiri Denemark <jdenemar@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com> 2019-02-22 14:45:24 +01:00			`<model fallback='forbid'>Broadwell-IBRS</model>`
cputest: Add data for Intel(R) Xeon(R) CPU E5-2623 v4 The CPU contains the updated microcode for CVE-2017-5715. The -guest.xml and -json.xml CPU definitions use Skylake-Client CPU model rather than Broadwell. This is similar to Xeon-E5-2650-v4 and it is caused by our CPU model selection code when no model matches the CPU signature (family + model). We'd need to maintain a complete list of CPU signatures for our CPU models to fix this. Signed-off-by: Jiri Denemark <jdenemar@redhat.com> Reviewed-by: Pavel Hrdina <phrdina@redhat.com> 2018-01-05 15:03:12 +01:00			`<vendor>Intel</vendor>`
cpu_map: Add more signatures for Broadwell CPU models This fixes several CPUs which were incorrectly detected as Skylake-Client. Signed-off-by: Jiri Denemark <jdenemar@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com> 2019-02-22 14:45:24 +01:00			`<feature policy='require' name='vme'/>`
cputest: Add data for Intel(R) Xeon(R) CPU E5-2623 v4 The CPU contains the updated microcode for CVE-2017-5715. The -guest.xml and -json.xml CPU definitions use Skylake-Client CPU model rather than Broadwell. This is similar to Xeon-E5-2650-v4 and it is caused by our CPU model selection code when no model matches the CPU signature (family + model). We'd need to maintain a complete list of CPU signatures for our CPU models to fix this. Signed-off-by: Jiri Denemark <jdenemar@redhat.com> Reviewed-by: Pavel Hrdina <phrdina@redhat.com> 2018-01-05 15:03:12 +01:00			`<feature policy='require' name='ss'/>`
cpu_map: Add more signatures for Broadwell CPU models This fixes several CPUs which were incorrectly detected as Skylake-Client. Signed-off-by: Jiri Denemark <jdenemar@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com> 2019-02-22 14:45:24 +01:00			`<feature policy='require' name='f16c'/>`
			`<feature policy='require' name='rdrand'/>`
cputest: Add data for Intel(R) Xeon(R) CPU E5-2623 v4 The CPU contains the updated microcode for CVE-2017-5715. The -guest.xml and -json.xml CPU definitions use Skylake-Client CPU model rather than Broadwell. This is similar to Xeon-E5-2650-v4 and it is caused by our CPU model selection code when no model matches the CPU signature (family + model). We'd need to maintain a complete list of CPU signatures for our CPU models to fix this. Signed-off-by: Jiri Denemark <jdenemar@redhat.com> Reviewed-by: Pavel Hrdina <phrdina@redhat.com> 2018-01-05 15:03:12 +01:00			`<feature policy='require' name='hypervisor'/>`
cpu_map: Add more signatures for Broadwell CPU models This fixes several CPUs which were incorrectly detected as Skylake-Client. Signed-off-by: Jiri Denemark <jdenemar@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com> 2019-02-22 14:45:24 +01:00			`<feature policy='require' name='arat'/>`
cputest: Add data for Intel(R) Xeon(R) CPU E5-2623 v4 The CPU contains the updated microcode for CVE-2017-5715. The -guest.xml and -json.xml CPU definitions use Skylake-Client CPU model rather than Broadwell. This is similar to Xeon-E5-2650-v4 and it is caused by our CPU model selection code when no model matches the CPU signature (family + model). We'd need to maintain a complete list of CPU signatures for our CPU models to fix this. Signed-off-by: Jiri Denemark <jdenemar@redhat.com> Reviewed-by: Pavel Hrdina <phrdina@redhat.com> 2018-01-05 15:03:12 +01:00			`<feature policy='require' name='tsc_adjust'/>`
cpu_map: Add more signatures for Broadwell CPU models This fixes several CPUs which were incorrectly detected as Skylake-Client. Signed-off-by: Jiri Denemark <jdenemar@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com> 2019-02-22 14:45:24 +01:00			`<feature policy='require' name='xsaveopt'/>`
cputest: Add data for Intel(R) Xeon(R) CPU E5-2623 v4 The CPU contains the updated microcode for CVE-2017-5715. The -guest.xml and -json.xml CPU definitions use Skylake-Client CPU model rather than Broadwell. This is similar to Xeon-E5-2650-v4 and it is caused by our CPU model selection code when no model matches the CPU signature (family + model). We'd need to maintain a complete list of CPU signatures for our CPU models to fix this. Signed-off-by: Jiri Denemark <jdenemar@redhat.com> Reviewed-by: Pavel Hrdina <phrdina@redhat.com> 2018-01-05 15:03:12 +01:00			`<feature policy='require' name='pdpe1gb'/>`
cpu_map: Add more signatures for Broadwell CPU models This fixes several CPUs which were incorrectly detected as Skylake-Client. Signed-off-by: Jiri Denemark <jdenemar@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com> 2019-02-22 14:45:24 +01:00			`<feature policy='require' name='abm'/>`
cputest: Add data for Intel(R) Xeon(R) CPU E5-2623 v4 The CPU contains the updated microcode for CVE-2017-5715. The -guest.xml and -json.xml CPU definitions use Skylake-Client CPU model rather than Broadwell. This is similar to Xeon-E5-2650-v4 and it is caused by our CPU model selection code when no model matches the CPU signature (family + model). We'd need to maintain a complete list of CPU signatures for our CPU models to fix this. Signed-off-by: Jiri Denemark <jdenemar@redhat.com> Reviewed-by: Pavel Hrdina <phrdina@redhat.com> 2018-01-05 15:03:12 +01:00			`</cpu>`