1. 11 12月, 2014 4 次提交
    • L
      Add the "-semihosting-config" option. · a38bb079
      Liviu Ionescu 提交于
      The usual semihosting behaviour is to process the system calls locally and
      return; unfortuantelly the initial implementation dinamically changed the
      target to GDB during debug sessions, which, for the usual arm-none-eabi-gdb,
      is not implemented. The result was that during debug sessions the semihosting
      calls were discarded.
      
      This patch adds a configuration variable and an option to set it on the
      command line:
      
          -semihosting-config [enable=on|off,]target=native|gdb|auto
      
      This option enables semihosting and defines where the semihosting calls will
      be addressed, to QEMU ('native') or to GDB ('gdb'). The default is auto, which
      means 'gdb' during debug sessions and 'native' otherwise.
      Signed-off-by: NLiviu Ionescu <ilg@livius.net>
      Message-id: 1416341957-9796-1-git-send-email-ilg@livius.net
      [PMM: moved declaration and definition of semihosting_target to
       gdbstub.h and gdbstub.c to fix build failure on linux-user]
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      a38bb079
    • L
      Pass semihosting exit code back to system. · 1ecc3a2d
      Liviu Ionescu 提交于
      In order to run unit tests under semihosting, it is necessary to pass the
      application exit code back to the system.
      
      ARM defines only the code to be used for non-error application exit
      (ADP_Stopped_ApplicationExit), all other codes should return non-zero
      exit codes.
      
      This patch checks if the application code passed via TARGET_SYS_EXIT is
      ADP_Stopped_ApplicationExit, and return 0, otherwise return 1.
      Signed-off-by: NLiviu Ionescu <ilg@livius.net>
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      1ecc3a2d
    • P
      Merge remote-tracking branch 'remotes/bkoppelmann/tags/pull-tricore-20141210' into staging · a09f2d16
      Peter Maydell 提交于
      TriCore BOL, BRC, BRN, BRR, RC, RCPW, RCRR, RCR, RLC and RCR insn added
      
      # gpg: Signature made Wed 10 Dec 2014 11:21:58 GMT using RSA key ID 6B69CA14
      # gpg: Good signature from "Bastian Koppelmann <kbastian@mail.uni-paderborn.de>"
      
      * remotes/bkoppelmann/tags/pull-tricore-20141210:
        target-tricore: Add instructions of RCR opcode format
        target-tricore: Add instructions of RLC opcode format
        target-tricore: Add instructions of RCPW, RCRR and RCRW opcode format
        target-tricore: Make TRICORE_FEATURES implying others.
        target-tricore: Add instructions of RC opcode format
        target-tricore: Add instructions of BRR opcode format
        target-tricore: Add instructions of BRN opcode format
        target-tricore: Add instructions of BRC opcode format
        target-tricore: Add instructions of BOL opcode format
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      a09f2d16
    • P
      Merge remote-tracking branch 'remotes/kraxel/tags/pull-vnc-20141210-1' into staging · 67a5eebc
      Peter Maydell 提交于
      vnc-enc-tight fix, keymaps code style.
      
      # gpg: Signature made Wed 10 Dec 2014 09:24:33 GMT using RSA key ID D3E87138
      # gpg: Good signature from "Gerd Hoffmann (work) <kraxel@redhat.com>"
      # gpg:                 aka "Gerd Hoffmann <gerd@kraxel.org>"
      # gpg:                 aka "Gerd Hoffmann (private) <kraxel@gmail.com>"
      
      * remotes/kraxel/tags/pull-vnc-20141210-1:
        keymaps: correct keymaps.c following Qemu coding style
        vnc-enc-tight: fix Arguments in wrong order
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      67a5eebc
  2. 10 12月, 2014 12 次提交
  3. 09 12月, 2014 1 次提交
  4. 04 12月, 2014 2 次提交
  5. 01 12月, 2014 4 次提交
  6. 28 11月, 2014 2 次提交
    • D
      Fix for crash after migration in virtio-rng on bi-endian targets · db12451d
      David Gibson 提交于
      VirtIO devices now remember which endianness they're operating in in order
      to support targets which may have guests of either endianness, such as
      powerpc.  This endianness state is transferred in a subsection of the
      virtio device's information.
      
      With virtio-rng this can lead to an abort after a loadvm hitting the
      assert() in virtio_is_big_endian().  This can be reproduced by doing a
      migrate and load from file on a bi-endian target with a virtio-rng device.
      The actual guest state isn't particularly important to triggering this.
      
      The cause is that virtio_rng_load_device() calls virtio_rng_process() which
      accesses the ring and thus needs the endianness.  However,
      virtio_rng_process() is called via virtio_load() before it loads the
      subsections.  Essentially the ->load callback in VirtioDeviceClass should
      only be used for actually reading the device state from the stream, not for
      post-load re-initialization.
      
      This patch fixes the bug by moving the virtio_rng_process() after the call
      to virtio_load().  Better yet would be to convert virtio to use vmsd and
      have the virtio_rng_process() as a post_load callback, but that's a bigger
      project for another day.
      
      This is bugfix, and should be considered for the 2.2 branch.
      Signed-off-by: NDavid Gibson <david@gibson.dropbear.id.au>
      Reviewed-by: NGreg Kurz <gkurz@linux.vnet.ibm.com>
      Message-id: 1417067290-20715-1-git-send-email-david@gibson.dropbear.id.au
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      db12451d
    • J
      virtio-net: fix unmap leak · 771b6ed3
      Jason Wang 提交于
      virtio_net_handle_ctrl() and other functions that process control vq
      request call iov_discard_front() which will shorten the iov. This will
      lead unmapping in virtqueue_push() leaks mapping.
      
      Fixes this by keeping the original iov untouched and using a temp variable
      in those functions.
      
      Cc: Wen Congyang <wency@cn.fujitsu.com>
      Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
      Cc: qemu-stable@nongnu.org
      Signed-off-by: NJason Wang <jasowang@redhat.com>
      Reviewed-by: NStefano Stabellini <stefano.stabellini@eu.citrix.com>
      Reviewed-by: NFam Zheng <famz@redhat.com>
      Reviewed-by: NMichael S. Tsirkin <mst@redhat.com>
      Message-id: 1417082643-23907-1-git-send-email-jasowang@redhat.com
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      771b6ed3
  7. 27 11月, 2014 2 次提交
    • M
      hmp: fix regression of HMP device_del auto-completion · 4cae4d5a
      Marcel Apfelbaum 提交于
      The commits:
       - 6a1fa9f5 (monitor: add del completion for peripheral device)
       - 66e56b13 (qdev: add qdev_build_hotpluggable_device_list helper)
      
      cause a QEMU crash when trying to use HMP device_del auto-completion.
      It can be easily reproduced by:
          <qemu-bin> -enable-kvm  ~/images/fedora.qcow2 -monitor stdio -device virtio-net-pci,id=vnet
      
          (qemu) device_del
          /home/mapfelba/git/upstream/qemu/hw/core/qdev.c:941:qdev_build_hotpluggable_device_list: Object 0x7f6ce04e4fe0 is not an instance of type device
          Aborted (core dumped)
      
      The root cause is qdev_build_hotpluggable_device_list going recursively over
      all peripherals and their children assuming all are devices. It doesn't work
      since PCI devices have at least on child which is a memory region (bus master).
      
      Solved by observing that all devices appear as direct children of
      /machine/peripheral container. No need of going recursively
      over all the children.
      Signed-off-by: NMarcel Apfelbaum <marcel.a@redhat.com>
      Reported-by: NGal Hammer <ghammer@redhat.com>
      Reviewed-by: NIgor Mammedov <imammedo@redhat.com>
      Message-id: 1417002601-20799-1-git-send-email-marcel.a@redhat.com
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      4cae4d5a
    • P
      qemu-timer: Avoid overflows when converting timeout to struct timespec · 490309fc
      Peter Maydell 提交于
      In qemu_poll_ns(), when we convert an int64_t nanosecond timeout into
      a struct timespec, we may accidentally run into overflow problems if
      the timeout is very long. This happens because the tv_sec field is a
      time_t, which is signed, so we might end up setting it to a negative
      value by mistake. This will result in what was intended to be a
      near-infinite timeout turning into an instantaneous timeout, and we'll
      busy loop. Cap the maximum timeout at INT32_MAX seconds (about 68 years)
      to avoid this problem.
      
      This specifically manifested on ARM hosts as an extreme slowdown on
      guest shutdown (when the guest reprogrammed the PL031 RTC to not
      generate alarms using a very long timeout) but could happen on other
      hosts and guests too.
      Reported-by: NChristoffer Dall <christoffer.dall@linaro.org>
      Cc: qemu-stable@nongnu.org
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      Reviewed-by: NFam Zheng <famz@redhat.com>
      Message-id: 1416939705-1272-1-git-send-email-peter.maydell@linaro.org
      490309fc
  8. 26 11月, 2014 6 次提交
  9. 25 11月, 2014 7 次提交