1. 21 10月, 2019 2 次提交
  2. 16 10月, 2019 3 次提交
  3. 15 10月, 2019 2 次提交
  4. 10 10月, 2019 2 次提交
    • D
      qemu: Add capability for the ccf-assist pSeries feature · 86a8e5a8
      Daniel Henrique Barboza 提交于
      Linux kernel 5.1 added a new PPC KVM capability named
      KVM_PPC_CPU_CHAR_BCCTR_FLUSH_ASSIST, which is exposed to the QEMU guest
      since QEMU commit 8ff43ee404d under a new sPAPR capability called
      SPAPR_CAP_CCF_ASSIST. This cap indicates whether the processor supports
      hardware acceleration for the count cache flush workaround, which
      is a software workaround that flushes the count cache on context
      switch. If the processor has this hardware acceleration, the software
      flush can be shortened, resulting in performance gain.
      
      This hardware acceleration is defaulted to 'off' in QEMU. The reason
      is that earlier versions of the Power 9 processor didn't support
      it (it is available on Power 9 DD2.3 and newer), and defaulting this
      option to 'on' would break migration compatibility between the Power 9
      processor class.
      
      However, the user running a P9 DD2.3+ hypervisor might want to create
      guests with ccf-assist=on, accepting the downside of only being able
      to migrate them only between other P9 DD2.3+ hosts running upstream
      kernel 5.1+, to get a performance boost.
      
      This patch adds this new capability to Libvirt, with the name of
      QEMU_CAPS_MACHINE_PSERIES_CAP_CCF_ASSIST.
      Reviewed-by: NCole Robinson <crobinso@redhat.com>
      Signed-off-by: NDaniel Henrique Barboza <danielhb413@gmail.com>
      86a8e5a8
    • J
      qemu: add ramfb capability · 9bfcf0f6
      Jonathon Jongsma 提交于
      Add a qemu capbility to see if the standalone ramfb device is available.
      Reviewed-by: NCole Robinson <crobinso@redhat.com>
      Signed-off-by: NJonathon Jongsma <jjongsma@redhat.com>
      9bfcf0f6
  5. 09 10月, 2019 1 次提交
  6. 07 10月, 2019 5 次提交
  7. 01 10月, 2019 1 次提交
  8. 30 9月, 2019 1 次提交
  9. 25 9月, 2019 1 次提交
  10. 19 9月, 2019 4 次提交
  11. 18 9月, 2019 2 次提交
  12. 12 9月, 2019 2 次提交
  13. 06 9月, 2019 2 次提交
  14. 23 8月, 2019 1 次提交
  15. 14 8月, 2019 1 次提交
  16. 07 8月, 2019 2 次提交
  17. 26 7月, 2019 1 次提交
    • J
      qemu: Translate features in virQEMUCapsGetCPUFeatures · 1fd28a2e
      Jiri Denemark 提交于
      Starting with QEMU 4.1 qemuMonitorCPUModelInfo structure in virQEMUCaps
      stores only canonical feature names which may differ from the name used
      by libvirt. We need translate these canonical names into libvirt names
      for further consumption.
      
      This fixes a bug in qemuConnectBaselineHypervisorCPU which would remove
      all features for which libvirt's spelling differs from the QEMU's
      preferred name. For example, the following result of
      qemuConnectBaselineHypervisorCPU on my host with QEMU 4.1 is wrong:
      
          <cpu mode='custom' match='exact'>
            <model fallback='forbid'>Skylake-Client</model>
            <vendor>Intel</vendor>
            <feature policy='require' name='ss'/>
            <feature policy='require' name='vmx'/>
            <feature policy='require' name='hypervisor'/>
            <feature policy='require' name='clflushopt'/>
            <feature policy='require' name='umip'/>
            <feature policy='require' name='arch-capabilities'/>
            <feature policy='require' name='xsaves'/>
            <feature policy='require' name='pdpe1gb'/>
            <feature policy='require' name='invtsc'/>
            <feature policy='disable' name='pclmuldq'/>
            <feature policy='disable' name='lahf_lm'/>
          </cpu>
      
      The 'pclmuldq' and 'lahf_lm' should not be disabled in the baseline CPU
      as they are supported by QEMU on this host.
      Signed-off-by: NJiri Denemark <jdenemar@redhat.com>
      Reviewed-by: NAndrea Bolognani <abologna@redhat.com>
      1fd28a2e
  18. 15 7月, 2019 1 次提交
  19. 20 6月, 2019 6 次提交