Skip to content
Snippets Groups Projects
  1. Dec 17, 2019
    • Markus Armbruster's avatar
      hw/misc/ivshmem: Bury dead legacy INTx code · e858e04d
      Markus Armbruster authored
      
      Devices "ivshmem-plain" and "ivshmem-doorbell" support only MSI-X.
      Config space register Interrupt Pin is zero.  Device "ivshmem"
      additionally supported legacy INTx, but it was removed in commit
      5a0e75f0 "hw/misc/ivshmem: Remove deprecated "ivshmem" legacy
      device".  The commit left ivshmem_update_irq() behind.  Since the
      Interrupt Pin register is zero, the function does nothing.  Remove it.
      
      Signed-off-by: default avatarMarkus Armbruster <armbru@redhat.com>
      Reviewed-by: default avatarThomas Huth <thuth@redhat.com>
      Message-Id: <20191205203557.11254-1-armbru@redhat.com>
      Signed-off-by: default avatarThomas Huth <thuth@redhat.com>
      e858e04d
    • Laurent Vivier's avatar
      pseries: disable migration-test if /dev/kvm cannot be used · 1ee5e144
      Laurent Vivier authored
      
      On ppc64, migration-test only works with kvm_hv, and we already
      have a check to verify the module is loaded.
      
      kvm_hv module can be loaded in memory and /sys/module/kvm_hv exists,
      but on some systems (like build systems) /dev/kvm can be missing
      (by administrators choice).
      
      And as kvm_hv exists test-migration is started but QEMU falls back to
      TCG because it cannot be used:
      
          Could not access KVM kernel module: No such file or directory
          failed to initialize KVM: No such file or directory
          Back to tcg accelerator
      
      And as the test is done with TCG, it fails.
      
      As for s390x, we must check for the existence and the access rights
      of /dev/kvm.
      
      Reported-by: default avatarCole Robinson <crobinso@redhat.com>
      Signed-off-by: default avatarLaurent Vivier <lvivier@redhat.com>
      Message-Id: <20191120170955.242900-1-lvivier@redhat.com>
      Reviewed-by: default avatarThomas Huth <thuth@redhat.com>
      Reviewed-by: default avatarGreg Kurz <groug@kaod.org>
      Reviewed-by: default avatarJuan Quintela <quintela@redhat.com>
      Signed-off-by: default avatarThomas Huth <thuth@redhat.com>
      1ee5e144
    • Cole Robinson's avatar
      tests: fix modules-test 'duplicate test case' error · eca3a945
      Cole Robinson authored
      
      ./configure --enable-sdl --audio-drv-list=sdl --enable-modules
      
      Will generate two identical test names: /$arch/module/load/sdl
      Which generates an error like:
      
      (tests/modules-test:23814): GLib-ERROR **: 18:23:06.359: duplicate test case path: /aarch64//module/load/sdl
      
      Add the subsystem prefix in the name as well, so instead we get:
      
      /$arch/module/load/audio-sdl
      /$arch/module/load/ui-sdl
      
      Signed-off-by: default avatarCole Robinson <crobinso@redhat.com>
      Message-Id: <d64c9aa098cc6e5c0b638438c4959eddfa7e24e2.1573679311.git.crobinso@redhat.com>
      Reviewed-by: default avatarMarc-André Lureau <marcandre.lureau@redhat.com>
      Reviewed-by: default avatarThomas Huth <thuth@redhat.com>
      Reviewed-by: default avatarPhilippe Mathieu-Daudé <philmd@redhat.com>
      Signed-off-by: default avatarThomas Huth <thuth@redhat.com>
      eca3a945
    • Thomas Huth's avatar
      Remove libbluetooth / bluez from the CI tests · 2831a7e5
      Thomas Huth authored
      
      Since the bluetooth code has been removed, we don't need to test
      with this library anymore.
      
      Message-Id: <20191120091014.16883-5-thuth@redhat.com>
      Acked-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: default avatarThomas Huth <thuth@redhat.com>
      2831a7e5
    • Thomas Huth's avatar
      Remove the core bluetooth code · 1d4ffe8d
      Thomas Huth authored
      
      It's been deprecated since QEMU v3.1. We've explicitly asked in the
      deprecation message that people should speak up on qemu-devel in case
      they are still actively using the bluetooth part of QEMU, but nobody
      ever replied that they are really still using it.
      
      I've tried it on my own to use this bluetooth subsystem for one of my
      guests, but I was also not able to get it running anymore: When I was
      trying to pass-through a real bluetooth device, either the guest did
      not see the device at all, or the guest crashed.
      
      Even worse for the emulated device: When running
      
       qemu-system-x86_64 -bt device:keyboard
      
      QEMU crashes once you hit a key.
      
      So it seems like the bluetooth stack is not only neglected, it is
      completely bitrotten, as far as I can tell. The only attention that
      this code got during the past years were some CVEs that have been
      spotted there. So this code is a burden for the developers, without
      any real benefit anymore. Time to remove it.
      
      Note: hw/bt/Kconfig only gets cleared but not removed here yet.
      Otherwise there is a problem with the *-softmmu/config-devices.mak.d
      dependency files - they still contain a reference to this file which
      gets evaluated first on some build hosts, before the file gets
      properly recreated. To avoid breaking these builders, we still need
      the file around for some time. It will get removed in a couple of
      weeks instead.
      
      Message-Id: <20191120091014.16883-4-thuth@redhat.com>
      Reviewed-by: default avatarJán Tomko <jtomko@redhat.com>
      Acked-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: default avatarThomas Huth <thuth@redhat.com>
      1d4ffe8d
  2. Dec 16, 2019
Loading