Skip to content

Q
qemu

openeuler / qemu

通知 10
Star 0
Fork 0
Q
qemu

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 31 10月, 2013 2 次提交
  3. 25 10月, 2013 2 次提交
  5. 18 10月, 2013 4 次提交
  7. 17 10月, 2013 6 次提交
  9. 11 10月, 2013 2 次提交
  11. 10 10月, 2013 2 次提交
  13. 09 10月, 2013 1 次提交
  15. 05 10月, 2013 2 次提交
  17. 04 10月, 2013 2 次提交
  19. 03 10月, 2013 9 次提交
    • A
      vfio: Fix debug output for int128 values · 1d5bf692
      由 Alexey Kardashevskiy 提交于 
      Memory regions can easily be 2^64 byte long and therefore overflow
for just a bit but that is enough for int128_get64() to assert.

This takes care of debug printing of huge section sizes.
Signed-off-by: NAlexey Kardashevskiy <aik@ozlabs.ru>
Signed-off-by: NAlex Williamson <alex.williamson@redhat.com>
      1d5bf692
    • A
      vfio-pci: Implement PCI hot reset · f16f39c3
      由 Alex Williamson 提交于 
      Now that VFIO has a PCI hot reset interface, take advantage of it.
There are two modes that we need to consider.  The first is when only
one device within the set of devices affected is actually assigned to
the guest.  In this case the other devices are are just held by VFIO
for isolation and we can pretend they're not there, doing an entire
bus reset whenever the device reset callback is triggered.  Supporting
this case separately allows us to do the best reset we can do of the
device even if the device is hotplugged.

The second mode is when multiple affected devices are all exposed to
the guest.  In this case we can only do a hot reset when the entire
system is being reset.  However, this also allows us to track which
individual devices are affected by a reset and only do them once.

We split our reset function into pre- and post-reset helper functions
prioritize the types of device resets available to us, and create
separate _one vs _multi reset interfaces to handle the distinct cases
above.
Signed-off-by: NAlex Williamson <alex.williamson@redhat.com>
      f16f39c3
    • J
      pci-ohci: Add missing 'break' in ohci_service_td · 4b351a0f
      由 Ján Veselý 提交于 
      Device communication errors need to be reported to driver.
Add a debug message while at it.
Signed-off-by: NJan Vesely <jano.vesely@gmail.com>
Acked-by: NGerd Hoffmann <kraxel@gmail.com>
Signed-off-by: NMichael Tokarev <mjt@tls.msk.ru>
      4b351a0f
    • G
      sh4: Fix serial line access for Linux kernels later than 3.2 · 84faf7c3
      由 Guenter Roeck 提交于 
      With Linux kernel version 3.3 or later, qemu fails with the following message:

sh_serial: unsupported read from 0x18
  Aborted
Reported-and-analyzed-by: NRob Landley <rob@landley.net>
Signed-off-by: NGuenter Roeck <linux@roeck-us.net>
Reviewed-by: NPeter Maydell <peter.maydell@linaro.org>
Signed-off-by: NMichael Tokarev <mjt@tls.msk.ru>
      84faf7c3
    • S
      hw/alpha: Fix compiler warning (integer constant is too large) · 9b2caaf4
      由 Stefan Weil 提交于 
      From buildbot default_i386_rhel61:

  CC    alpha-softmmu/hw/alpha/typhoon.o
hw/alpha/typhoon.c: In function 'typhoon_translate_iommu':
hw/alpha/typhoon.c:703: warning: integer constant is too large for 'long' type
hw/alpha/typhoon.c:703: warning: integer constant is too large for 'long' type
Signed-off-by: NStefan Weil <sw@weilnetz.de>
Acked-by: NRichard Henderson <rth@twiddle.net>
Signed-off-by: NMichael Tokarev <mjt@tls.msk.ru>
      9b2caaf4
    • A
      vfio-pci: Cleanup error_reports · 8fbf47c3
      由 Alex Williamson 提交于 
      Remove carriage returns and tweak formatting for error_reports.
Signed-off-by: NAlex Williamson <alex.williamson@redhat.com>
      8fbf47c3
    • A
      vfio-pci: Lazy PCI option ROM loading · 6f864e6e
      由 Alex Williamson 提交于 
      During vfio-pci initfn, the device is not always in a state where the
option ROM can be read.  In the case of graphics cards, there's often
no per function reset, which means we have host driver state affecting
whether the option ROM is usable.  Ideally we want to move reading the
option ROM past any co-assigned device resets to the point where the
guest first tries to read the ROM itself.

To accomplish this, we switch the memory region for the option rom to
an I/O region rather than a memory mapped region.  This has the side
benefit that we don't waste KVM memory slots for a BAR where we don't
care about performance.  This also allows us to delay loading the ROM
from the device until the first read by the guest.  We then use the
PCI config space size of the ROM BAR when setting up the BAR through
QEMU PCI.

Another benefit of this approach is that previously when a user set
the ROM to a file using the romfile= option, we still probed VFIO for
the parameters of the ROM, which can result in dmesg errors about an
invalid ROM.  We now only probe VFIO to get the ROM contents if the
guest actually tries to read the ROM.
Signed-off-by: NAlex Williamson <alex.williamson@redhat.com>
      6f864e6e
    • A
      vfio-pci: Test device reset capabilities · befe5176
      由 Alex Williamson 提交于 
      Not all resets are created equal.  PM reset is not very reliable,
especially for GPUs, so we might want to opt for a bus reset if a
standard reset will only do a D3hot->D0 transition.  We can also
use this to tell if the standard reset will do a bus reset (if
neither has_pm_reset or has_flr is probed, but the device still
supports reset).
Signed-off-by: NAlex Williamson <alex.williamson@redhat.com>
      befe5176
    • A
      vfio-pci: Add support for MSI affinity · c7679d45
      由 Alex Williamson 提交于 
      When MSI is accelerated through KVM the vectors are only programmed
when the guest first enables MSI support.  Subsequent writes to the
vector address or data fields are ignored.  Unfortunately that means
we're ignore updates done to adjust SMP affinity of the vectors.
MSI SMP affinity already works in non-KVM mode because the address
and data fields are read from their backing store on each interrupt.

This patch stores the MSIMessage programmed into KVM so that we can
determine when changes are made and update the routes.
Signed-off-by: NAlex Williamson <alex.williamson@redhat.com>
      c7679d45
  21. 29 9月, 2013 5 次提交
  23. 26 9月, 2013 2 次提交
  25. 24 9月, 2013 1 次提交