1. 24 10月, 2019 2 次提交
  2. 22 10月, 2019 4 次提交
  3. 21 9月, 2019 1 次提交
    • C
      pc: Add an SMB0 ACPI device to q35 · ebe15582
      Corey Minyard 提交于
      This is so I2C devices can be found in the ACPI namespace.  Currently
      that's only IPMI, but devices can be easily added now.
      
      Adding the devices required some PCI information, and the bus itself
      to be added to the PCMachineState structure.
      
      Note that this only works on Q35, the ACPI for PIIX4 is not capable
      of handling an SMBus device.
      
      Cc: Michael S. Tsirkin <mst@redhat.com>
      Cc: Igor Mammedov <imammedo@redhat.com>
      Signed-off-by: NCorey Minyard <cminyard@mvista.com>
      Reviewed-by: NPaolo Bonzini <pbonzini@redhat.com>
      ebe15582
  4. 21 8月, 2019 1 次提交
  5. 16 8月, 2019 3 次提交
  6. 06 7月, 2019 1 次提交
    • E
      i386: Make unversioned CPU models be aliases · 0788a56b
      Eduardo Habkost 提交于
      This will make unversioned CPU models behavior depend on the
      machine type:
      
      * "pc-*-4.0" and older will not report them as aliases.
        This is done to keep compatibility with older QEMU versions
        after management software starts translating aliases.
      
      * "pc-*-4.1" will translate unversioned CPU models to -v1.
        This is done to keep compatibility with existing management
        software, that still relies on CPU model runnability promises.
      
      * "none" will translate unversioned CPU models to their latest
        version.  This is planned become the default in future machine
        types (probably in pc-*-4.3).
      Signed-off-by: NEduardo Habkost <ehabkost@redhat.com>
      Message-Id: <20190628002844.24894-8-ehabkost@redhat.com>
      Reviewed-by: NDaniel P. Berrangé <berrange@redhat.com>
      Signed-off-by: NEduardo Habkost <ehabkost@redhat.com>
      0788a56b
  7. 21 6月, 2019 1 次提交
    • G
      hw: Nuke hw_compat_4_0_1 and pc_compat_4_0_1 · 8e8cbed0
      Greg Kurz 提交于
      Commit c87759ce fixed a regression affecting pc-q35 machines by
      introducing a new pc-q35-4.0.1 machine version to be used instead
      of pc-q35-4.0. The only purpose was to revert the default behaviour
      of not using split irqchip, but the change also introduced the usual
      hw_compat and pc_compat bits, and wired them for pc-q35 only.
      
      This raises questions when it comes to add new compat properties for
      4.0* machine versions of any architecture. Where to add them ? In
      4.0, 4.0.1 or both ? Error prone. Another possibility would be to teach
      all other architectures about 4.0.1. This solution isn't satisfying,
      especially since this is a pc-q35 specific issue.
      
      It turns out that the split irqchip default is handled in the machine
      option function and doesn't involve compat lists at all.
      
      Drop all the 4.0.1 compat lists and use the 4.0 ones instead in the 4.0.1
      machine option function.
      
      Move the compat props that were added to the 4.0.1 since c87759ce to
      4.0.
      
      Even if only hw_compat_4_0_1 had an impact on other architectures,
      drop pc_compat_4_0_1 as well for consistency.
      
      Fixes: c87759ce "q35: Revert to kernel irqchip"
      Suggested-by: NDr. David Alan Gilbert <dgilbert@redhat.com>
      Signed-off-by: NGreg Kurz <groug@kaod.org>
      Reviewed-by: NDr. David Alan Gilbert <dgilbert@redhat.com>
      Reviewed-by: NMichael S. Tsirkin <mst@redhat.com>
      Message-Id: <156051774276.244890.8660277280145466396.stgit@bahia.lan>
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      8e8cbed0
  8. 03 6月, 2019 1 次提交
    • A
      q35: Revert to kernel irqchip · c87759ce
      Alex Williamson 提交于
      Commit b2fc91db ("q35: set split kernel irqchip as default") changed
      the default for the pc-q35-4.0 machine type to use split irqchip, which
      turned out to have disasterous effects on vfio-pci INTx support.  KVM
      resampling irqfds are registered for handling these interrupts, but
      these are non-functional in split irqchip mode.  We can't simply test
      for split irqchip in QEMU as userspace handling of this interrupt is a
      significant performance regression versus KVM handling (GeForce GPUs
      assigned to Windows VMs are non-functional without forcing MSI mode or
      re-enabling kernel irqchip).
      
      The resolution is to revert the change in default irqchip mode in the
      pc-q35-4.1 machine and create a pc-q35-4.0.1 machine for the 4.0-stable
      branch.  The qemu-q35-4.0 machine type should not be used in vfio-pci
      configurations for devices requiring legacy INTx support without
      explicitly modifying the VM configuration to use kernel irqchip.
      
      Link: https://bugs.launchpad.net/qemu/+bug/1826422
      Fixes: b2fc91db ("q35: set split kernel irqchip as default")
      Signed-off-by: NAlex Williamson <alex.williamson@redhat.com>
      Reviewed-by: NPeter Xu <peterx@redhat.com>
      Message-Id: <155786484688.13873.6037015630912983760.stgit@gimli.home>
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      c87759ce
  9. 26 4月, 2019 1 次提交
  10. 11 3月, 2019 1 次提交
  11. 28 2月, 2019 2 次提交
  12. 05 2月, 2019 1 次提交
  13. 08 1月, 2019 1 次提交
  14. 07 1月, 2019 14 次提交
  15. 21 12月, 2018 1 次提交
  16. 20 12月, 2018 1 次提交
  17. 12 12月, 2018 2 次提交
  18. 20 11月, 2018 1 次提交
  19. 02 7月, 2018 1 次提交