1. 22 12月, 2015 6 次提交
  2. 18 12月, 2015 1 次提交
    • P
      kvm: x86: add support for KVM_CAP_SPLIT_IRQCHIP · 15eafc2e
      Paolo Bonzini 提交于
      This patch adds support for split IRQ chip mode. When
      KVM_CAP_SPLIT_IRQCHIP is enabled:
      
          1.) The PIC, PIT, and IOAPIC are implemented in userspace while
          the LAPIC is implemented by KVM.
      
          2.) The software IOAPIC delivers interrupts to the KVM LAPIC via
          kvm_set_irq. Interrupt delivery is configured via the MSI routing
          table, for which routes are reserved in target-i386/kvm.c then
          configured in hw/intc/ioapic.c
      
          3.) KVM delivers IOAPIC EOIs via a new exit KVM_EXIT_IOAPIC_EOI,
          which is handled in target-i386/kvm.c and relayed to the software
          IOAPIC via ioapic_eoi_broadcast.
      Signed-off-by: NMatt Gingell <gingell@google.com>
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      15eafc2e
  3. 18 11月, 2015 1 次提交
    • E
      target-i386: Disable rdtscp on Opteron_G* CPU models · 33b5e8c0
      Eduardo Habkost 提交于
      KVM can't virtualize rdtscp on AMD CPUs yet, so there's no point
      in enabling it by default on AMD CPU models, as all we are
      getting are confused users because of the "host doesn't support
      requested feature" warnings.
      
      Disable rdtscp on Opteron_G* models, but keep compatibility on
      pc-*-2.4 and older (just in case there are people are doing funny
      stuff using AMD CPU models on Intel hosts).
      Signed-off-by: NEduardo Habkost <ehabkost@redhat.com>
      33b5e8c0
  4. 06 11月, 2015 4 次提交
    • E
      target-i386: Remove POPCNT from qemu64 and qemu32 CPU models · 6aa91e4a
      Eduardo Habkost 提交于
      POPCNT is not available on Penryn and older and on Opteron_G2 and older,
      and we want to make the default CPU runnable in most hosts, so it won't
      be enabled by default in KVM mode.
      
      We should eventually have all features supported by TCG enabled by
      default in TCG mode, but as we don't have a good mechanism today to
      ensure we have different defaults in KVM and TCG mode, disable POPCNT in
      the qemu64 and qemu32 CPU models entirely.
      Reviewed-by: NPaolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: NEduardo Habkost <ehabkost@redhat.com>
      6aa91e4a
    • E
      target-i386: Remove ABM from qemu64 CPU model · 71195672
      Eduardo Habkost 提交于
      ABM is not available on Sandy Bridge and older, and we want to make the
      default CPU runnable in most hosts, so it won't be enabled by default in
      KVM mode.
      
      We should eventually have all features supported by TCG enabled by
      default in TCG mode, but as we don't have a good mechanism today to
      ensure we have different defaults in KVM and TCG mode, disable ABM in
      the qemu64 CPU model entirely.
      Reviewed-by: NPaolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: NEduardo Habkost <ehabkost@redhat.com>
      71195672
    • E
      target-i386: Remove SSE4a from qemu64 CPU model · 0909ad24
      Eduardo Habkost 提交于
      SSE4a is not available in any Intel CPU, and we want to make the default
      CPU runnable in most hosts, so it doesn't make sense to enable it by
      default in KVM mode.
      
      We should eventually have all features supported by TCG enabled by
      default in TCG mode, but as we don't have a good mechanism today to
      ensure we have different defaults in KVM and TCG mode, disable SSE4a in
      the qemu64 CPU model entirely.
      Reviewed-by: NPaolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: NEduardo Habkost <ehabkost@redhat.com>
      0909ad24
    • E
      target-i386: Set "check=off" by default on pc-*-2.4 and older · 3e684822
      Eduardo Habkost 提交于
      The default CPU model (qemu64) have some issues today: it enables some
      features (ABM and SSE4a) that are not present in many host CPUs. That
      means many hosts (but not all of them) had those features silently
      disabled in the default configuration in QEMU 2.4 and older.
      
      With the new "check=on" default, this causes warnings to be printed in
      the default configuration, because of the lack of SSE4A on all Intel
      hosts, and the lack of ABM on Sandy Bridge and older hosts:
      
        $ qemu-system-x86_64 -machine pc,accel=kvm
        warning: host doesn't support requested feature: CPUID.80000001H:ECX.abm [bit 5]
        warning: host doesn't support requested feature: CPUID.80000001H:ECX.sse4a [bit 6]
      
      Those issues will be fixed in pc-*-2.5 and newer. But as we can't change
      the guest ABI in pc-*-2.4, disable "check" mode by default in pc-*-2.4
      and older so we don't print spurious warnings.
      Reviewed-by: NPaolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: NEduardo Habkost <ehabkost@redhat.com>
      3e684822
  5. 29 10月, 2015 1 次提交
  6. 23 10月, 2015 1 次提交
  7. 22 10月, 2015 1 次提交
  8. 03 10月, 2015 2 次提交
  9. 02 10月, 2015 1 次提交
  10. 25 9月, 2015 2 次提交
  11. 24 9月, 2015 1 次提交
  12. 10 9月, 2015 3 次提交
  13. 08 9月, 2015 1 次提交
  14. 13 8月, 2015 11 次提交
  15. 04 8月, 2015 1 次提交
  16. 16 7月, 2015 1 次提交
  17. 08 7月, 2015 1 次提交
  18. 07 7月, 2015 1 次提交