1. 27 7月, 2015 15 次提交
  2. 24 7月, 2015 17 次提交
  3. 23 7月, 2015 8 次提交
    • P
      Merge remote-tracking branch 'remotes/ehabkost/tags/numa-pull-request' into staging · 12e21eb0
      Peter Maydell 提交于
      NUMA queue, 2015-07-22
      
      # gpg: Signature made Wed Jul 22 19:11:04 2015 BST using RSA key ID 984DC5A6
      # gpg: Good signature from "Eduardo Habkost <ehabkost@redhat.com>"
      # gpg: WARNING: This key is not certified with sufficiently trusted signatures!
      # gpg:          It is not certain that the signature belongs to the owner.
      # Primary key fingerprint: 5A32 2FD5 ABC4 D3DB ACCF  D1AA 2807 936F 984D C5A6
      
      * remotes/ehabkost/tags/numa-pull-request:
        hostmem: Fix qemu_opt_get_bool() crash in host_memory_backend_init()
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      12e21eb0
    • N
      qemu-char: Fix missed data on unix socket · 4bf1cb03
      Nils Carlson 提交于
      Commit 812c1057 introduced HUP detection on unix and tcp sockets prior
      to a read in tcp_chr_read. This unfortunately broke CloudStack 4.2
      which relied on the old behaviour where data on a socket was readable
      even if a HUP was present.
      
      A working solution is to properly check the return values from recv,
      handling a closed socket once there is no more data to read.
      
      Also enable polling for G_IO_NVAL to ensure the callback is called
      for all possible events as these should now be possible to handle
      with the improved error detection.
      Signed-off-by: NNils Carlson <pyssling@ludd.ltu.se>
      Message-Id: <1437338396-22336-1-git-send-email-pyssling@ludd.ltu.se>
      [Do not handle EINTR; use socket_error(). - Paolo]
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      4bf1cb03
    • P
      9172f428
    • P
      exec.c: Use atomic_rcu_read() to access dispatch in memory_region_section_get_iotlb() · 0b8e2c10
      Peter Maydell 提交于
      When accessing the dispatch pointer in an AddressSpace within an RCU
      critical section we should always use atomic_rcu_read(). Fix an
      access within memory_region_section_get_iotlb() which was incorrectly
      doing a direct pointer access.
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      Message-Id: <1437391637-31576-1-git-send-email-peter.maydell@linaro.org>
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      0b8e2c10
    • A
      vfio/pci: Fix bootindex · 759b484c
      Alex Williamson 提交于
      bootindex was incorrectly changed to a device Property during the
      platform code split, resulting in it no longer working.  Remove it.
      Signed-off-by: NAlex Williamson <alex.williamson@redhat.com>
      Cc: qemu-stable@nongnu.org # v2.3+
      759b484c
    • A
      vfio/pci: Fix RTL8168 NIC quirks · 69970fce
      Alex Williamson 提交于
      The RTL8168 quirk correctly describes using bit 31 as a signal to
      mark a latch/completion, but the code mistakenly uses bit 28.  This
      causes the Realtek driver to spin on this register for quite a while,
      20k cycles on Windows 7 v7.092 driver.  Then it gets frustrated and
      tries to set the bit itself and spins for another 20k cycles.  For
      some this still results in a working driver, for others not.  About
      the only thing the code really does in its current form is protect
      the guest from sneaking in writes to the real hardware MSI-X table.
      The fix is obviously to use bit 31 as we document that we should.
      
      The other problem doesn't seem to affect current drivers as nobody
      seems to use these window registers for writes to the MSI-X table, but
      we need to use the stored data when a write is triggered, not the
      value of the current write, which only provides the offset.
      
      Note that only the Windows drivers from Realtek seem to use these
      registers, the Microsoft drivers provided with Windows 8.1 do not
      access them, nor do Linux in-kernel drivers.
      
      Link: https://bugs.launchpad.net/qemu/+bug/1384892Signed-off-by: NAlex Williamson <alex.williamson@redhat.com>
      Cc: qemu-stable@nongnu.org # v2.1+
      69970fce
    • E
      hostmem: Fix qemu_opt_get_bool() crash in host_memory_backend_init() · 6b269967
      Eduardo Habkost 提交于
      This fixes the following crash, introduced by commit
      49d2e648:
      
        $ gdb --args qemu-system-x86_64 -machine pc,mem-merge=off -object memory-backend-ram,id=ram-node0,size=1024
        [...]
        Program received signal SIGABRT, Aborted.
        (gdb) bt
        #0  0x00007ffff253b8c7 in raise () at /lib64/libc.so.6
        #1  0x00007ffff253d52a in abort () at /lib64/libc.so.6
        #2  0x00007ffff253446d in __assert_fail_base () at /lib64/libc.so.6
        #3  0x00007ffff2534522 in  () at /lib64/libc.so.6
        #4  0x00005555558bb80a in qemu_opt_get_bool_helper (opts=0x55555621b650, name=name@entry=0x5555558ec922 "mem-merge", defval=defval@entry=true, del=del@entry=false) at qemu/util/qemu-option.c:388
        #5  0x00005555558bbb5a in qemu_opt_get_bool (opts=<optimized out>, name=name@entry=0x5555558ec922 "mem-merge", defval=defval@entry=true) at qemu/util/qemu-option.c:398
        #6  0x0000555555720a24 in host_memory_backend_init (obj=0x5555562ac970) at qemu/backends/hostmem.c:226
      
      Instead of using qemu_opt_get_bool(), that didn't work with
      qemu_machine_opts for a long time, we can use the corresponding
      MachineState fields.
      Reviewed-by: NMarcel Apfelbaum <marcel@redhat.com>
      Signed-off-by: NEduardo Habkost <ehabkost@redhat.com>
      6b269967
    • P
      Update version for v2.4.0-rc2 release · b69b3053
      Peter Maydell 提交于
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      b69b3053