1. 23 5月, 2016 5 次提交
  2. 21 5月, 2016 21 次提交
  3. 20 5月, 2016 2 次提交
  4. 19 5月, 2016 12 次提交
    • P
      Merge remote-tracking branch 'remotes/kevin/tags/for-upstream' into staging · 6bd8ab68
      Peter Maydell 提交于
      Block layer patches
      
      # gpg: Signature made Thu 19 May 2016 16:09:27 BST using RSA key ID C88F2FD6
      # gpg: Good signature from "Kevin Wolf <kwolf@redhat.com>"
      
      * remotes/kevin/tags/for-upstream: (31 commits)
        qemu-iotests: Fix regression in 136 on aio_read invalid
        qemu-iotests: Simplify 109 with unaligned qemu-img compare
        qemu-io: Fix recent UI updates
        block: clarify error message for qmp-eject
        qemu-iotests: Some more write_zeroes tests
        qcow2: Fix write_zeroes with partially allocated backing file cluster
        qcow2: fix condition in is_zero_cluster
        block: Propagate AioContext change to all children
        block: Remove BlockDriverState.blk
        block: Don't return throttling info in query-named-block-nodes
        block: Avoid bs->blk in bdrv_next()
        block: Add bdrv_has_blk()
        block: Remove bdrv_aio_multiwrite()
        blockjob: Don't touch BDS iostatus
        blockjob: Don't set iostatus of target
        block: User BdrvChild callback for device name
        block: Use BdrvChild callbacks for change_media/resize
        block: Don't check throttled reqs in bdrv_requests_pending()
        Revert "block: Forbid I/O throttling on nodes with multiple parents for 2.6"
        block: Remove bdrv_move_feature_fields()
        ...
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      6bd8ab68
    • K
      Merge remote-tracking branch 'mreitz/tags/pull-block-for-kevin-2016-05-19' into queue-block · 7753da23
      Kevin Wolf 提交于
      Block patches
      
      # gpg: Signature made Thu May 19 16:58:53 2016 CEST using RSA key ID E838ACAD
      # gpg: Good signature from "Max Reitz <mreitz@redhat.com>"
      
      * mreitz/tags/pull-block-for-kevin-2016-05-19:
        qemu-iotests: Fix regression in 136 on aio_read invalid
        qemu-iotests: Simplify 109 with unaligned qemu-img compare
        qemu-io: Fix recent UI updates
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      7753da23
    • E
      qemu-iotests: Fix regression in 136 on aio_read invalid · 37546ff2
      Eric Blake 提交于
      Commit 093ea232 removed the ability for aio_read and aio_write
      to artificially inflate the invalid statistics counters for
      block devices, since it no longer flags unaligned offset or
      length.  Add 'aio_read -i' and 'aio_write -i' to restore
      the ability, and update test 136 to use it.
      Reported-by: NKevin Wolf <kwolf@redhat.com>
      Signed-off-by: NEric Blake <eblake@redhat.com>
      Message-id: 1463416983-28318-4-git-send-email-eblake@redhat.com
      Signed-off-by: NMax Reitz <mreitz@redhat.com>
      37546ff2
    • E
      qemu-iotests: Simplify 109 with unaligned qemu-img compare · 9e28bb26
      Eric Blake 提交于
      For some time now, qemu-img compare has been able to compare
      unaligned images.  So we no longer need test 109's hack of
      resizing to sector boundaries before invoking compare.
      Signed-off-by: NEric Blake <eblake@redhat.com>
      Reviewed-by: NMax Reitz <mreitz@redhat.com>
      Message-id: 1463416983-28318-3-git-send-email-eblake@redhat.com
      Signed-off-by: NMax Reitz <mreitz@redhat.com>
      9e28bb26
    • E
      qemu-io: Fix recent UI updates · 4ca1d340
      Eric Blake 提交于
      Commit 770e0e0e [*] tried to add 'writev -f', but didn't tweak
      the getopt() call to actually let it work.  Likewise, commit
      c2e001cc missed implementing 'aio_write -u -z'.  The latter commit
      also introduced a leak of ctx.
      
      [*] does it sound "ech0e" in here? :)
      Signed-off-by: NEric Blake <eblake@redhat.com>
      Message-id: 1463416983-28318-2-git-send-email-eblake@redhat.com
      Signed-off-by: NMax Reitz <mreitz@redhat.com>
      4ca1d340
    • P
      Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging · 776efef3
      Peter Maydell 提交于
      NEED_CPU_H cleanups, big enough to deserve their own pull request.
      
      # gpg: Signature made Thu 19 May 2016 15:42:37 BST using RSA key ID 78C7AE83
      # gpg: Good signature from "Paolo Bonzini <bonzini@gnu.org>"
      # gpg:                 aka "Paolo Bonzini <pbonzini@redhat.com>"
      
      * remotes/bonzini/tags/for-upstream: (52 commits)
        hw: clean up hw/hw.h includes
        hw: remove pio_addr_t
        cpu: move exec-all.h inclusion out of cpu.h
        exec: extract exec/tb-context.h
        hw: explicitly include qemu/log.h
        mips: move CP0 functions out of cpu.h
        arm: move arm_log_exception into .c file
        qemu-common: push cpu.h inclusion out of qemu-common.h
        acpi: do not use TARGET_PAGE_SIZE
        s390x: reorganize CSS bits between cpu.h and other headers
        dma: do not depend on kvm_enabled()
        gdbstub: remove unnecessary includes from gdbstub-xml.c
        qemu-common: stop including qemu/host-utils.h from qemu-common.h
        qemu-common: stop including qemu/bswap.h from qemu-common.h
        cpu: move endian-dependent load/store functions to cpu-all.h
        hw: cannot include hw/hw.h from user emulation
        hw: move CPU state serialization to migration/cpu.h
        hw: do not use VMSTATE_*TL
        include: poison symbols in osdep.h
        apic: move target-dependent definitions to cpu.h
        ...
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      776efef3
    • J
      block: clarify error message for qmp-eject · 3a3086b7
      John Snow 提交于
      If you use HMP's eject but the CDROM tray is locked, you may get a
      confusing error message informing you that the "tray isn't open."
      
      As this is the point of eject, we can do a little better and help
      clarify that the tray was locked and that it (might) open up later,
      so try again.
      
      It's not ideal, but it makes the semantics of the (legacy) eject
      command more understandable to end users when they try to use it.
      Signed-off-by: NJohn Snow <jsnow@redhat.com>
      Reviewed-by: NEric Blake <eblake@redhat.com>
      Reviewed-by: NFam Zheng <famz@redhat.com>
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      3a3086b7
    • K
      qemu-iotests: Some more write_zeroes tests · 1ef7d010
      Kevin Wolf 提交于
      This covers some more write_zeroes cases which are relevant for the
      recent qcow2 optimisations that check the allocation status of the
      backing file for partial cluster write_zeroes requests.
      
      This needs to be separate from 034 because we can only support qcow2 in
      this test case for multiple reasons: We check the allocation status
      after write_zeroes with 'qemu-img map' and the optimised behaviour that
      produces zero clusters is only implemented in qcow2; second, the map
      command returns offsets that are qcow2 specific; and finally, we also
      use 512 byte clusters which aren't supported for formats like qed.
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      Reviewed-by: NEric Blake <eblake@redhat.com>
      1ef7d010
    • K
      qcow2: Fix write_zeroes with partially allocated backing file cluster · 5efdf532
      Kevin Wolf 提交于
      In order to correctly check whether a given cluster is read as zero, we
      don't only need to check whether bdrv_get_block_status_above() sets
      BDRV_BLOCK_ZERO, but also if all sectors for the whole cluster have the
      same status.
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      Reviewed-by: NEric Blake <eblake@redhat.com>
      Reviewed-by: NDenis V. Lunev <den@openvz.org>
      5efdf532
    • D
      qcow2: fix condition in is_zero_cluster · f575f145
      Denis V. Lunev 提交于
      We should check for (res & BDRV_BLOCK_ZERO) only. The situation when we
      will have !(res & BDRV_BLOCK_DATA) and will not have BDRV_BLOCK_ZERO is
      not possible for images with bdi.unallocated_blocks_are_zero == true.
      
      For those images where it's false, however, it can happen and we must
      not consider the data zeroed then or we would corrupt the image.
      Signed-off-by: NDenis V. Lunev <den@openvz.org>
      CC: Kevin Wolf <kwolf@redhat.com>
      Reviewed-by: NEric Blake <eblake@redhat.com>
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      f575f145
    • M
      block: Propagate AioContext change to all children · b97511c7
      Max Reitz 提交于
      Instead of propagating any change of a BDS's AioContext only to its file
      and backing children and letting driver-specific code do the rest, just
      propagate it to all and drop the thus superfluous implementations of
      bdrv_{at,de}tach_aio_context() in Quorum, blkverify and VMDK.
      Signed-off-by: NMax Reitz <mreitz@redhat.com>
      Reviewed-by: NPaolo Bonzini <pbonzini@redhat.com>
      Reviewed-by: NAlberto Garcia <berto@igalia.com>
      Reviewed-by: NStefan Hajnoczi <stefanha@redhat.com>
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      b97511c7
    • K
      block: Remove BlockDriverState.blk · 1f0c461b
      Kevin Wolf 提交于
      This patch removes the remaining users of bs->blk, which will allow us
      to have multiple BBs on top of a single BDS. In the meantime, all checks
      that are currently in place to prevent the user from creating such
      setups can be switched to bdrv_has_blk() instead of accessing BDS.blk.
      
      Future patches can allow them and e.g. enable users to mirror to a block
      device that already has a BlockBackend on it.
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      Reviewed-by: NMax Reitz <mreitz@redhat.com>
      1f0c461b