1. 09 3月, 2015 4 次提交
    • D
      pseries: Limit PCI host bridge "index" value · 3e4ac968
      David Gibson 提交于
      pseries guests can have large numbers of PCI host bridges.  To avoid the
      user having to specify a number of different configuration values for every
      one, the device supports an "index" property which is a shorthand setting
      the various window and configuration addresses from a predefined sensible
      set.
      
      There are some problems with the details at present:
        * The "index" propery is signed, but negative values will create PCI
      windows below where we expect, potentially colliding with other devices
        * No limit is imposed on the "index" property and large values can
      translate to extremely large window addresses.  With PCI passthrough in
      particular this can mean we exceed various mapping and physical address
      limits causing the guest host bridge to not work in strange ways.
      
      This patch addresses this, by making "index" unsigned, and imposing a
      limit.  Currently the limit allows indices from 0..255 which is probably
      enough host bridges for the time being.  It's fairly easy to extend if
      we discover we need more.
      Signed-off-by: NDavid Gibson <david@gibson.dropbear.id.au>
      Reviewed-by: NPaolo Bonzini <pbonzini@redhat.com>
      Reviewed-by: NMichael Roth <mdroth@linux.vnet.ibm.com>
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      3e4ac968
    • A
      target-ppc: Use right page size with hash table lookup · ad3e67d0
      Aneesh Kumar K.V 提交于
      We look at two sizes specified in ISA (4K, 64K). If not found matching,
      we consider it 16MB.
      
      Without this patch we would fail to lookup address above 16MB range.
      Below 16MB happened to work before because the kernel have a liner
      mapping and we always looked up hash for 0xc000000000000000. The
      actual real address was computed by using the 16MB offset
      with the real address found with the above hash.
      
      Without Fix:
      (gdb) x/16x 0xc000000001000000
      0xc000000001000000 <list_entries+453208>:       Cannot access memory at address 0xc000000001000000
      (gdb)
      
      With Fix:
      (gdb)  x/16x 0xc000000001000000
      0xc000000001000000 <list_entries+453208>:       0x00000000      0x00000000      0x00000000      0x00000000
      0xc000000001000010 <list_entries+453224>:       0x00000000      0x00000000      0x00000000      0x00000000
      0xc000000001000020 <list_entries+453240>:       0x00000000      0x00000000      0x00000000      0x00000000
      0xc000000001000030 <list_entries+453256>:       0x00000000      0x00000000      0x00000000      0x00000000
      Signed-off-by: NAneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
      Reviewed-by: NDavid Gibson <david@gibson.dropbear.id.au>
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      ad3e67d0
    • A
      spapr_vio/spapr_iommu: Move VIO bypass where it belongs · ee9a569a
      Alexey Kardashevskiy 提交于
      Instead of tweaking a TCE table device by adding there a bypass flag,
      let's add an alias to RAM and IOMMU memory region, and enable/disable
      those according to the selected bypass mode.
      This way IOMMU memory region can have size of the actual window rather
      than ram_size which is essential for upcoming DDW support.
      
      This moves bypass logic to VIO layer and keeps @bypass flag in TCE table
      for migration compatibility only. This replaces spapr_tce_set_bypass()
      calls with explicit assignment to avoid confusion as the function could
      do something more that just syncing the @bypass flag.
      
      This adds a pointer to VIO device into the sPAPRTCETable struct to provide
      the sPAPRTCETable device a way to update bypass mode for the VIO device.
      Signed-off-by: NAlexey Kardashevskiy <aik@ozlabs.ru>
      Reviewed-by: NDavid Gibson <david@gibson.dropbear.id.au>
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      ee9a569a
    • P
      Merge remote-tracking branch 'remotes/mst/tags/for_upstream' into staging · 0048fa6c
      Peter Maydell 提交于
      pci, pc, virtio fixes and cleanups
      
      A bunch of fixes all over the place.
      All of ACPI refactoring has been merged.
      Legacy pci commands have been dropped.
      virtio header cleanup
      initial patches from virtio-1.0 branch
      Signed-off-by: NMichael S. Tsirkin <mst@redhat.com>
      
      * remotes/mst/tags/for_upstream: (130 commits)
        acpi: drop unused code
        aml-build: comment fix
        acpi-build: fix typo in comment
        acpi: update generated files
        vhost user:support vhost user nic for non msi guests
        aml-build: fix build for glib < 2.22
        acpi: update generated files
        Makefile.target: binary depends on config-devices
        acpi-test-data: update after pci rewrite
        acpi, mem-hotplug: use PC_DIMM_SLOT_PROP in acpi_memory_plug_cb().
        pci-hotplug-old: Has been dead for five major releases, bury
        pci: Give a few helpers internal linkage
        acpi: make build_*() routines static to aml-build.c
        pc: acpi: remove not used anymore ssdt-[misc|pcihp].hex.generated blobs
        pc: acpi-build: drop template patching and create PCI bus tree dynamically
        tests: ACPI: update pc/SSDT.bridge due to new alg of PCI tree creation
        pc: acpi-build: simplify PCI bus tree generation
        tests: add ACPI blobs for qemu with bridge cases
        tests: bios-tables-test: add support for testing bridges
        tests: ACPI test blobs update due to PCI0._CRS changes
        ...
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      
      Conflicts:
      	hw/pci/pci-hotplug-old.c
      0048fa6c
  2. 08 3月, 2015 9 次提交
  3. 07 3月, 2015 3 次提交
  4. 05 3月, 2015 5 次提交
  5. 04 3月, 2015 6 次提交
  6. 03 3月, 2015 13 次提交
    • P
      vl: take iothread lock very early · 576a94d8
      Paolo Bonzini 提交于
      If the iothread lock isn't taken by the main thread, the RCU callbacks
      might run concurrently with the main thread.  QEMU's not ready for that.
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      Tested-by: NChristian Borntraeger <borntraeger@de.ibm.com>
      Tested-by: NGonglei <arei.gonglei@huawei.com>
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      576a94d8
    • P
      Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging · 3180aadb
      Peter Maydell 提交于
      - more config options
      - bootdevice, iscsi, virtio-scsi fixes
      - build system patches for MinGW and config-devices.mak
      - qemu_mutex_lock_iothread deadlock fixes
      - another tiny patch from the record/replay series
      
      # gpg: Signature made Mon Mar  2 09:59:14 2015 GMT using RSA key ID 78C7AE83
      # gpg: Good signature from "Paolo Bonzini <bonzini@gnu.org>"
      # gpg:                 aka "Paolo Bonzini <pbonzini@redhat.com>"
      # gpg: WARNING: This key is not certified with a trusted signature!
      # gpg:          There is no indication that the signature belongs to the owner.
      # Primary key fingerprint: 46F5 9FBD 57D6 12E7 BFD4  E2F7 7E15 100C CD36 69B1
      #      Subkey fingerprint: F133 3857 4B66 2389 866C  7682 BFFB D25F 78C7 AE83
      
      * remotes/bonzini/tags/for-upstream:
        cpus: be more paranoid in avoiding deadlocks
        cpus: fix deadlock and segfault in qemu_mutex_lock_iothread
        virtio-scsi: Allocate op blocker reason before blocking
        Makefile.target: binary depends on config-devices
        Makefile: don't silence mak file test with V=1
        Makefile: fix up parallel building under MSYS+MinGW
        iscsi: Handle write protected case in reopen
        Give ivshmem its own config option
        Create specific config option for "platform-bus"
        Add specific config options for PCI-E bridges
        bootdevice: fix segment fault when booting guest with '-kernel' and '-initrd'
        timer: replace time() with QEMU_CLOCK_HOST
        virtio-scsi-dataplane: Call blk_set_aio_context within BQL
        block: Forbid bdrv_set_aio_context outside BQL
        scsi: give device a parent before setting properties
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      3180aadb
    • L
      xhci: generate a Transfer Event for each Transfer TRB with the IOC bit set · aa685789
      Laszlo Ersek 提交于
      At the moment, when the XHCI driver in edk2
      (MdeModulePkg/Bus/Pci/XhciDxe/XhciDxe.inf) runs on QEMU, with the options
      
        -device nec-usb-xhci -device usb-kbd
      
      it crashes with:
      
        ASSERT MdeModulePkg/Bus/Pci/XhciDxe/XhciSched.c(1759):
        TrsRing != ((void*) 0)
      
      The crash hits in the following edk2 call sequence (all files under
      MdeModulePkg/Bus/):
      
      UsbEnumerateNewDev()                         [Usb/UsbBusDxe/UsbEnumer.c]
        UsbBuildDescTable()                        [Usb/UsbBusDxe/UsbDesc.c]
          UsbGetDevDesc()                          [Usb/UsbBusDxe/UsbDesc.c]
            UsbCtrlGetDesc(USB_REQ_GET_DESCRIPTOR) [Usb/UsbBusDxe/UsbDesc.c]
              UsbCtrlRequest()                     [Usb/UsbBusDxe/UsbDesc.c]
                UsbHcControlTransfer()             [Usb/UsbBusDxe/UsbUtility.c]
                  XhcControlTransfer()             [Pci/XhciDxe/Xhci.c]
                    XhcCreateUrb()                 [Pci/XhciDxe/XhciSched.c]
                      XhcCreateTransferTrb()       [Pci/XhciDxe/XhciSched.c]
                    XhcExecTransfer()              [Pci/XhciDxe/XhciSched.c]
                      XhcCheckUrbResult()          [Pci/XhciDxe/XhciSched.c]
                        //
                        // look for TRB_TYPE_DATA_STAGE event [1]
                        //
                    //
                    // Store a copy of the device descriptor, as the hub device
                    // needs this info to configure endpoint. [2]
                    //
        UsbSetConfig()                             [Usb/UsbBusDxe/UsbDesc.c]
          UsbCtrlRequest(USB_REQ_SET_CONFIG)       [Usb/UsbBusDxe/UsbDesc.c]
            UsbHcControlTransfer()                 [Usb/UsbBusDxe/UsbUtility.c]
              XhcControlTransfer()                 [Pci/XhciDxe/Xhci.c]
                XhcSetConfigCmd()                  [Pci/XhciDxe/XhciSched.c]
                  XhcInitializeEndpointContext()   [Pci/XhciDxe/XhciSched.c]
                    //
                    // allocate transfer ring for the endpoint [3]
                    //
      
      USBKeyboardDriverBindingStart()              [Usb/UsbKbDxe/EfiKey.c]
        UsbIoAsyncInterruptTransfer()              [Usb/UsbBusDxe/UsbBus.c]
          UsbHcAsyncInterruptTransfer()            [Usb/UsbBusDxe/UsbUtility.c]
            XhcAsyncInterruptTransfer()            [Pci/XhciDxe/Xhci.c]
              XhcCreateUrb()                       [Pci/XhciDxe/Xhci.c]
                XhcCreateTransferTrb()             [Pci/XhciDxe/XhciSched.c]
                  XhcSyncTrsRing()                 [Pci/XhciDxe/XhciSched.c]
                    ASSERT (TrsRing != NULL) [4]
      
      UsbEnumerateNewDev() in the USB bus driver issues a GET_DESCRIPTOR
      request, in order to determine the number of configurations that the
      endpoint supports. The requests consists of three stages (three TRBs),
      setup, data, and status. The length of the response is determined in [1],
      namely from the transfer event that the host controller generates in
      response to the request's middle stage (ie. the data stage).
      
      If the length of the answer is correct (a full GET_DESCRIPTOR request
      takes 18 bytes), then the XHCI driver that underlies the USB bus driver
      "snoops" (caches) the descriptor data for later [2].
      
      Later, the USB bus driver sends a SET_CONFIG request. The underlying XHCI
      driver allocates a transfer ring for the endpoint, relying on the data
      snooped and cached in step [2].
      
      Finally, the USB keyboard driver submits an asynchronous interrupt
      transfer to manage the keyboard. As part of this it asserts [4] that the
      ring has been allocated in step [3].
      
      And this ASSERT() fires. The root cause can be found in the way QEMU
      handles the initial GET_DESCRIPTOR request.
      
      Again, that request consists of three stages (TRBs, Transfer Request
      Blocks), "setup", "data", and "status". The XhcCreateTransferTrb()
      function sets the IOC ("Interrupt on Completion") flag in each of these
      TRBs.
      
      According to the XHCI specification, the host controller shall generate a
      Transfer Event in response to *each* individual TRB of the request that
      had the IOC flag set. This means that QEMU should queue three events:
      setup, data, and status, for edk2's XHCI driver.
      
      However, QEMU only generates two events:
      - one for the setup (ie. 1st) stage,
      - another for the status (ie. 3rd) stage.
      
      No event is generated for the middle (ie. data) stage. The loop in QEMU's
      xhci_xfer_report() function runs three times, but due to the "reported"
      variable, only the first and the last TRBs elicit events, the middle (data
      stage) results in no event queued.
      
      As a consequence:
      - When handling the GET_DESCRIPTOR request, XhcCheckUrbResult() in [1]
        does not update the response length from zero.
      
      - XhcControlTransfer() thinks that the response is invalid (it has zero
        length payload instead of 18 bytes), hence [2] is not reached; the
        device descriptor is not stashed for later, and the number of possible
        configurations is left at zero.
      
      - When handling the SET_CONFIG request, (NumConfigurations == 0) from
        above prevents the allocation of the endpoint's transfer ring.
      
      - When the keyboard driver tries to use the endpoint, the ASSERT() blows
        up.
      
      The solution is to correct the emulation in QEMU, and to generate a
      transfer event whenever IOC is set in a TRB.
      
      The patch replaces
      
        !reported && (IOC || foo)    == !reported && IOC ||
                                        !reported && foo
      
      with
      
        IOC || (!reported && foo)    == IOC ||
                                        !reported && foo
      
      which only changes how
      
        reported && IOC
      
      is handled. (Namely, it now generates an event.)
      
      Tested with edk2 built for "qemu-system-aarch64 -M virt" (ie.
      "ArmVirtualizationQemu.dsc", aka "AAVMF"), and guest Linux.
      Signed-off-by: NLaszlo Ersek <lersek@redhat.com>
      Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      aa685789
    • C
    • G
      qxl: drop update_displaychangelistener call for secondary qxl devices · 20ca3763
      Gerd Hoffmann 提交于
      Commit 3dcadce5 added three
      update_displaychangelistener call sites:
      
      Two for primary qxl cards, when entering/leaving vga mode, which are
      correct.
      
      One for secondary qxl cards, which is wrong because we don't register
      a displaychangelistener in the first place for secondary cards.
      
      Remove it.
      Reported-by: NBrad Campbell <lists2009@fnarfbargle.com>
      Tested-by: NBrad Campbell <lists2009@fnarfbargle.com>
      Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      20ca3763
    • R
      vga: refactor vram_size clamping and rounding · 619616ce
      Radim Krčmář 提交于
      Make the code a bit more obvious.
      
      We don't have min/max, so a general helper for clamp probably isn't
      acceptable either.
      Signed-off-by: NRadim Krčmář <rkrcmar@redhat.com>
      Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      619616ce
    • R
      qxl: refactor rounding up to a nearest power of 2 · bb7443f6
      Radim Krčmář 提交于
      We already have pow2floor, mirror it and use instead of a function with
      similar results (same in used domain), to clarify our intent.
      Signed-off-by: NRadim Krčmář <rkrcmar@redhat.com>
      Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      bb7443f6
    • R
      spice: fix invalid memory access to vga.vram · 876d5163
      Radim Krčmář 提交于
      vga_common_init() doesn't allow more than 256 MiB vram size and silently
      shrinks any larger value.  qxl_dirty_surfaces() used the unshrinked size
      via qxl->shadow_rom.surface0_area_size when accessing the memory, which
      resulted in segfault.
      
      Add a workaround for this case and an assert if it happens again.
      
      We have to bump the vga memory limit too, because 256 MiB wouldn't have
      allowed 8k (it requires more than 128 MiB).
      1024 MiB doesn't work, but 512 MiB seems fine.
      Proposed-by: NGerd Hoffmann <kraxel@redhat.com>
      Signed-off-by: NRadim Krčmář <rkrcmar@redhat.com>
      Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      876d5163
    • R
      qxl: document minimal video memory for new modes · 03d9825d
      Radim Krčmář 提交于
      The alternative to removing existing comments.
      Signed-off-by: NRadim Krčmář <rkrcmar@redhat.com>
      Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      03d9825d
    • G
      bootdevice: add check in restore_boot_order() · 76349f5b
      Gonglei 提交于
      qemu_boot_set() can't fail in restore_boot_order(),
      then simply assert it doesn't fail, by passing
      &error_abort if boot_set_handler set.
      Suggested-by: NMarkus Armbruster <armbru@redhat.com>
      Signed-off-by: NGonglei <arei.gonglei@huawei.com>
      Reviewed-by: NMarkus Armbruster <armbru@redhat.com>
      76349f5b
    • G
      bootdevice: check boot order argument validation before vm running · f05f47bb
      Gonglei 提交于
      Either 'once' option or 'order' option can take effect for -boot at
      the same time, that is say initial startup processing can check only
      one. And pc.c's set_boot_dev() fails when its boot order argument
      is invalid. This patch provide a solution fix this problem:
      
       1. If "once" is given, register reset handler to restore boot order.
      
       2. Pass the normal boot order to machine creation.  Should fail when
         the normal boot order is invalid.
      
       3. If "once" is given, set it with qemu_boot_set().  Fails when the
         once boot order is invalid.
      
       4. Start the machine.
      
       5. On reset, the reset handler calls qemu_boot_set() to restore boot
         order.  Should never fail.
      Suggested-by: NMarkus Armbruster <armbru@redhat.com>
      Signed-off-by: NGonglei <arei.gonglei@huawei.com>
      Reviewed-by: NMarkus Armbruster <armbru@redhat.com>
      f05f47bb
    • P
      Merge remote-tracking branch 'remotes/armbru/tags/pull-error-2015-02-26' into staging · 5efde22a
      Peter Maydell 提交于
      QemuOpts: Convert various setters to Error
      
      # gpg: Signature made Thu Feb 26 13:56:43 2015 GMT using RSA key ID EB918653
      # gpg: Good signature from "Markus Armbruster <armbru@redhat.com>"
      # gpg:                 aka "Markus Armbruster <armbru@pond.sub.org>"
      
      * remotes/armbru/tags/pull-error-2015-02-26:
        qtest: Use qemu_opt_set() instead of qemu_opts_parse()
        pc: Use qemu_opt_set() instead of qemu_opts_parse()
        qemu-sockets: Simplify setting numeric and boolean options
        block: Simplify setting numeric options
        qemu-img: Suppress unhelpful extra errors in convert, amend
        QemuOpts: Propagate errors through opts_parse()
        QemuOpts: Propagate errors through opts_do_parse()
        QemuOpts: Drop qemu_opt_set(), rename qemu_opt_set_err(), fix use
        block: Suppress unhelpful extra errors in bdrv_img_create()
        qemu-img: Suppress unhelpful extra errors in convert, resize
        QemuOpts: Convert qemu_opts_set() to Error, fix its use
        QemuOpts: Convert qemu_opt_set_number() to Error, fix its use
        QemuOpts: Convert qemu_opt_set_bool() to Error, fix its use
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      5efde22a
    • B
      target-tricore: Add instructions of RRR1 opcode format, which have 0xc3 as first opcode · bebe80fc
      Bastian Koppelmann 提交于
      Add helpers helper_addsur_h/_ssov which adds one halfword and subtracts one
      halfword, rounds / and saturates each half word independently.
      
      Add microcode helper functions:
          * gen_maddsu_h/sus_h: multiply two halfwords left justified and add to the
                                first one word and subtract from the second one word
                                / and saturate each resulting word independetly.
          * gen_maddsum_h/sums_h: multiply two halfwords in q-format left justified
                                  and add to the first one word and subtract from
                                  the second one word / and saturate each resulting
                                  word independetly.
          * gen_maddsur32_h/32s_h: multiply two halfwords in q-format left justified
                                   and add to the first one word and subtract from
                                   the second one word, round both results / and
                                   saturate each resulting word independetly.
      Signed-off-by: NBastian Koppelmann <kbastian@mail.uni-paderborn.de>
      Reviewed-by: NRichard Henderson <rth@twiddle.net>
      bebe80fc