[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-commits] [qemu/qemu] dc80ca: virtio-blk: avoid qdev property defin
|
From: |
GitHub |
|
Subject: |
[Qemu-commits] [qemu/qemu] dc80ca: virtio-blk: avoid qdev property definition duplica... |
|
Date: |
Tue, 01 Jul 2014 06:30:06 -0700 |
Branch: refs/heads/master
Home: https://github.com/qemu/qemu
Commit: dc80ca6cd6cafdee174af3c883d85e19b7fd70a5
https://github.com/qemu/qemu/commit/dc80ca6cd6cafdee174af3c883d85e19b7fd70a5
Author: Stefan Hajnoczi <address@hidden>
Date: 2014-07-01 (Tue, 01 Jul 2014)
Changed paths:
M include/hw/virtio/virtio-blk.h
Log Message:
-----------
virtio-blk: avoid qdev property definition duplication
It becomes unwiedly to duplicate all virtio-blk qdev property
definitions due to an #ifdef. The C preprocessor syntax makes it a
little hard to resolve this cleanly but we can extract the #ifdef and
call a macro it defines later.
Avoiding duplication is important since it will only get worse when we
move the x-data-plane qdev property here too. We'd have a combinatorial
explosion since x-data-plane has its own #ifdef.
Suggested-by: Peter Crosthwaite <address@hidden>
Signed-off-by: Stefan Hajnoczi <address@hidden>
Reviewed-by: Peter Crosthwaite <address@hidden>
Commit: a9968c77d5a56211ae22be2e6a1dcb07f2016010
https://github.com/qemu/qemu/commit/a9968c77d5a56211ae22be2e6a1dcb07f2016010
Author: Cornelia Huck <address@hidden>
Date: 2014-07-01 (Tue, 01 Jul 2014)
Changed paths:
M hw/block/dataplane/virtio-blk.c
Log Message:
-----------
dataplane: bail out on unsupported transport
If the virtio transport does not support notifiers (like s390-virtio),
we can't use dataplane. Bail out early and let the user know what is
wrong.
Signed-off-by: Cornelia Huck <address@hidden>
Reviewed-by: Stefan Hajnoczi <address@hidden>
Signed-off-by: Stefan Hajnoczi <address@hidden>
Commit: ee512c6f21b2f76ae923e3a4cabbd58899ff7ae1
https://github.com/qemu/qemu/commit/ee512c6f21b2f76ae923e3a4cabbd58899ff7ae1
Author: Stefan Hajnoczi <address@hidden>
Date: 2014-07-01 (Tue, 01 Jul 2014)
Changed paths:
M hw/s390x/virtio-ccw.c
M hw/virtio/virtio-pci.c
M include/hw/virtio/virtio-blk.h
Log Message:
-----------
virtio-blk: move x-data-plane qdev property to virtio-blk.h
Move the x-data-plane property. Originally it was outside since not
every transport may wish to support dataplane. But that makes little
sense when we have a dedicated CONFIG_VIRTIO_BLK_DATA_PLANE ifdef
already.
This move makes it easier to switch to property aliases in the next
patch.
Signed-off-by: Stefan Hajnoczi <address@hidden>
Reviewed-by: Peter Crosthwaite <address@hidden>
Commit: 67cc7e0aaca835ed68cf3bd34f4d51a21232792f
https://github.com/qemu/qemu/commit/67cc7e0aaca835ed68cf3bd34f4d51a21232792f
Author: Stefan Hajnoczi <address@hidden>
Date: 2014-07-01 (Tue, 01 Jul 2014)
Changed paths:
M hw/core/qdev.c
M include/hw/qdev-properties.h
Log Message:
-----------
qdev: add qdev_alias_all_properties()
The qdev_alias_all_properties() function creates QOM alias properties
for each qdev property on a DeviceState. This is useful for parent
objects that wish to forward property accesses to their children.
Signed-off-by: Stefan Hajnoczi <address@hidden>
Reviewed-by: Peter Crosthwaite <address@hidden>
Commit: caffdac363801cd2cf2bf01ad013a8c1e1e43800
https://github.com/qemu/qemu/commit/caffdac363801cd2cf2bf01ad013a8c1e1e43800
Author: Stefan Hajnoczi <address@hidden>
Date: 2014-07-01 (Tue, 01 Jul 2014)
Changed paths:
M hw/s390x/s390-virtio-bus.c
M hw/s390x/s390-virtio-bus.h
M hw/s390x/virtio-ccw.c
M hw/s390x/virtio-ccw.h
M hw/virtio/virtio-pci.c
M hw/virtio/virtio-pci.h
Log Message:
-----------
virtio-blk: use aliases instead of duplicate qdev properties
virtio-blk-pci, virtio-blk-s390, and virtio-blk-ccw all duplicate the
qdev properties of their VirtIOBlock child. This approach does not work
well with string or pointer properties since we must be careful about
leaking or double-freeing them.
Use the QOM alias property to forward property accesses to the
VirtIOBlock child. This way no duplication is necessary.
Remember to stop calling virtio_blk_set_conf() so that we don't clobber
the values already set on the VirtIOBlock instance.
Signed-off-by: Stefan Hajnoczi <address@hidden>
Reviewed-by: Peter Crosthwaite <address@hidden>
Commit: f7fedda84a8eb316c99a9de647c4844b862a7b38
https://github.com/qemu/qemu/commit/f7fedda84a8eb316c99a9de647c4844b862a7b38
Author: Stefan Hajnoczi <address@hidden>
Date: 2014-07-01 (Tue, 01 Jul 2014)
Changed paths:
M hw/block/virtio-blk.c
M include/hw/virtio/virtio-blk.h
Log Message:
-----------
virtio-blk: drop virtio_blk_set_conf()
This function is no longer used since parent objects now use child
aliases to set the VirtIOBlkConf directly.
Signed-off-by: Stefan Hajnoczi <address@hidden>
Reviewed-by: Peter Crosthwaite <address@hidden>
Commit: c5d49db4469dfc0cc7f4c01dfb4ed4e8b96bdbcd
https://github.com/qemu/qemu/commit/c5d49db4469dfc0cc7f4c01dfb4ed4e8b96bdbcd
Author: Stefan Hajnoczi <address@hidden>
Date: 2014-07-01 (Tue, 01 Jul 2014)
Changed paths:
M hw/s390x/s390-virtio-bus.c
M hw/s390x/virtio-ccw.c
M hw/virtio/virtio-pci.c
Log Message:
-----------
virtio: fix virtio-blk child refcount in transports
object_initialize() leaves the object with a refcount of 1.
object_property_add_child() adds its own reference which is dropped
again when the property is deleted.
The upshot of this is that we always have a refcount >= 1. Upon hot
unplug the virtio-blk child is not finalized!
Drop our reference after the child property has been added to the
parent.
Signed-off-by: Stefan Hajnoczi <address@hidden>
Reviewed-by: Peter Crosthwaite <address@hidden>
Commit: 32a877e4059ad7fd428bdd31d3e954fed72fa21b
https://github.com/qemu/qemu/commit/32a877e4059ad7fd428bdd31d3e954fed72fa21b
Author: Stefan Hajnoczi <address@hidden>
Date: 2014-07-01 (Tue, 01 Jul 2014)
Changed paths:
M hw/block/virtio-blk.c
M include/hw/virtio/virtio-blk.h
Log Message:
-----------
virtio-blk: move qdev properties into virtio-blk.c
There is no need to make DEFINE_VIRTIO_BLK_PROPERTIES() public. Inline
it into virtio-blk.c so it cannot be used by mistake from other source
files.
Signed-off-by: Stefan Hajnoczi <address@hidden>
Reviewed-by: Peter Crosthwaite <address@hidden>
Commit: 467b3f33e9b094bf6db5a4d6e6905f077edca0fb
https://github.com/qemu/qemu/commit/467b3f33e9b094bf6db5a4d6e6905f077edca0fb
Author: Stefan Hajnoczi <address@hidden>
Date: 2014-07-01 (Tue, 01 Jul 2014)
Changed paths:
M hw/block/virtio-blk.c
M hw/s390x/s390-virtio-bus.c
M hw/s390x/virtio-ccw.c
M hw/virtio/virtio-pci.c
Log Message:
-----------
virtio-blk: replace x-iothread with iothread link property
Up until now -device virtio-blk-pci,x-iothread=<id> was used to assign
an IOThread. This was a temporary solution while we cleaned up QOM link
properties.
This patch switches over to a QOM link property since it is now possible
to restrict the setter to unrealized instances and automatically unref
the IOThread when the virtio-blk-pci device is freed.
Since the "iothread" property is a QOM property and not a qdev property,
we must alias it explicitly for virtio-blk-pci, as well as CCW and
s390-virtio.
Signed-off-by: Stefan Hajnoczi <address@hidden>
Commit: 1351d1ec89eabebc9fdff20451a62c413d7accc1
https://github.com/qemu/qemu/commit/1351d1ec89eabebc9fdff20451a62c413d7accc1
Author: Stefan Hajnoczi <address@hidden>
Date: 2014-07-01 (Tue, 01 Jul 2014)
Changed paths:
M hw/core/qdev-properties-system.c
M include/hw/qdev-properties.h
Log Message:
-----------
qdev: drop iothread property type
The iothread property type is no longer used and can be removed.
Signed-off-by: Stefan Hajnoczi <address@hidden>
Commit: 8698e110f8aa1cdf8ba1afdda8f2658333a4ab01
https://github.com/qemu/qemu/commit/8698e110f8aa1cdf8ba1afdda8f2658333a4ab01
Author: Stefan Hajnoczi <address@hidden>
Date: 2014-07-01 (Tue, 01 Jul 2014)
Changed paths:
M hw/block/dataplane/virtio-blk.c
Log Message:
-----------
virtio-blk: remove need for explicit x-data-plane=on option
The x-data-plane=on|off option is no longer useful because the
iothread=<iothread> option conveys the same information plus which
IOThread to use.
Do not delete x-data-plane=on|off yet as a convenience to people using
this legacy experimental option. We will drop it in QEMU 2.2.
Instead, turn on data-plane when either x-data-plane=on or
iothread=<iothread> are used. The following command-line uses
data-plane:
qemu -device virtio-blk-pci,iothread=foo,drive=drive0
Signed-off-by: Stefan Hajnoczi <address@hidden>
Commit: 4ab1559085d688dddf4de77f1ead3102e243e668
https://github.com/qemu/qemu/commit/4ab1559085d688dddf4de77f1ead3102e243e668
Author: Chunyan Liu <address@hidden>
Date: 2014-07-01 (Tue, 01 Jul 2014)
Changed paths:
M block/qed.c
M block/raw-posix.c
M block/vdi.c
M block/vmdk.c
M block/vpc.c
M include/block/block_int.h
M qemu-doc.texi
M qemu-img.texi
M tests/qemu-iotests/082.out
Log Message:
-----------
qemu-img create: add 'nocow' option
Add 'nocow' option so that users could have a chance to set NOCOW flag to
newly created files. It's useful on btrfs file system to enhance performance.
Btrfs has low performance when hosting VM images, even more when the guest
in those VM are also using btrfs as file system. One way to mitigate this bad
performance is to turn off COW attributes on VM files. Generally, there are
two ways to turn off NOCOW on btrfs: a) by mounting fs with nodatacow, then
all newly created files will be NOCOW. b) per file. Add the NOCOW file
attribute. It could only be done to empty or new files.
This patch tries the second way, according to the option, it could add NOCOW
per file.
For most block drivers, since the create file step is in raw-posix.c, so we
can do setting NOCOW flag ioctl in raw-posix.c only.
But there are some exceptions, like block/vpc.c and block/vdi.c, they are
creating file by calling qemu_open directly. For them, do the same setting
NOCOW flag ioctl work in them separately.
[Fixed up 082.out due to the new 'nocow' creation option
--Stefan]
Signed-off-by: Chunyan Liu <address@hidden>
Signed-off-by: Stefan Hajnoczi <address@hidden>
Commit: 214a081a0dd44e69f7db4a741880a8ae9d174fa2
https://github.com/qemu/qemu/commit/214a081a0dd44e69f7db4a741880a8ae9d174fa2
Author: Max Reitz <address@hidden>
Date: 2014-07-01 (Tue, 01 Jul 2014)
Changed paths:
M tests/qemu-iotests-quick.sh
Log Message:
-----------
iotests: Simplify qemu-iotests-quick.sh
As of the "iotests: Allow out-of-tree run" series, the qemu-iotests may
(and should) be run directly in the build tree and will then guess the
binary paths themselves. Therefore, qemu-iotests-quick.sh does not need
to (and should not) enter the source path anymore; also, it does not
need to specify the binaries because "check" will guess them
automatically.
As a side-effect, tests using qemu may now be added to the quick group.
Signed-off-by: Max Reitz <address@hidden>
Signed-off-by: Stefan Hajnoczi <address@hidden>
Commit: ee9dd1fc901f7098a1c2af5a2202bd7f41124dbc
https://github.com/qemu/qemu/commit/ee9dd1fc901f7098a1c2af5a2202bd7f41124dbc
Author: Max Reitz <address@hidden>
Date: 2014-07-01 (Tue, 01 Jul 2014)
Changed paths:
M tests/qemu-iotests/group
Log Message:
-----------
iotests: Add qemu tests to quick group
Now that qemu-iotests-quick.sh supports tests using the qemu binary, we
are free to add such tests to the quick group.
Signed-off-by: Max Reitz <address@hidden>
Signed-off-by: Stefan Hajnoczi <address@hidden>
Commit: c891e3bbc5bc3d74ad0ba896852a9796ceb147c2
https://github.com/qemu/qemu/commit/c891e3bbc5bc3d74ad0ba896852a9796ceb147c2
Author: Max Reitz <address@hidden>
Date: 2014-07-01 (Tue, 01 Jul 2014)
Changed paths:
M tests/qemu-iotests/group
Log Message:
-----------
iotests: Add more tests to quick group
While at it, add some more tests to the quick group (those that run with
-nocache in under three seconds on my HDD).
Signed-off-by: Max Reitz <address@hidden>
Signed-off-by: Stefan Hajnoczi <address@hidden>
Commit: 7676e2c597000eff3a7233b40cca768b358f9bc9
https://github.com/qemu/qemu/commit/7676e2c597000eff3a7233b40cca768b358f9bc9
Author: Jeff Cody <address@hidden>
Date: 2014-07-01 (Tue, 01 Jul 2014)
Changed paths:
M blockdev.c
M qapi/block-core.json
M qmp-commands.hx
M tests/qemu-iotests/040
Log Message:
-----------
block: make 'top' argument to block-commit optional
Now that active layer block-commit is supported, the 'top' argument
no longer needs to be mandatory.
Change it to optional, with the default being the active layer in the
device chain.
[kwolf: Rebased and resolved conflict in tests/qemu-iotests/040]
Reviewed-by: Eric Blake <address@hidden>
Reviewed-by: Benoit Canet <address@hidden>
Signed-off-by: Jeff Cody <address@hidden>
Signed-off-by: Kevin Wolf <address@hidden>
Signed-off-by: Stefan Hajnoczi <address@hidden>
Commit: 4caf0fcd45db46920a6264b1621ae6adc772ef19
https://github.com/qemu/qemu/commit/4caf0fcd45db46920a6264b1621ae6adc772ef19
Author: Jeff Cody <address@hidden>
Date: 2014-07-01 (Tue, 01 Jul 2014)
Changed paths:
M block.c
Log Message:
-----------
block: simplify bdrv_find_base() and bdrv_find_overlay()
This simplifies the function bdrv_find_overlay(). With this change,
bdrv_find_base() is just a subset of usage of bdrv_find_overlay(),
so this also takes advantage of that.
Reviewed-by: Eric Blake <address@hidden>
Reviewed-by: Benoit Canet <address@hidden>
Signed-off-by: Jeff Cody <address@hidden>
Signed-off-by: Stefan Hajnoczi <address@hidden>
Commit: 6764579f894950afe87d8ec3b323adde8925d4fd
https://github.com/qemu/qemu/commit/6764579f894950afe87d8ec3b323adde8925d4fd
Author: Peter Maydell <address@hidden>
Date: 2014-07-01 (Tue, 01 Jul 2014)
Changed paths:
M block/cow.c
Log Message:
-----------
block/cow: Avoid use of uninitialized cow_bs in error path
Commit 25814e8987 introduced an error-exit code path which does
a "goto exit" before the cow_bs variable is initialized, meaning
we would call bdrv_unref() on an uninitialized variable and
likely segfault. Fix this by moving the NULL-initialization
to the top of the function and making the exit code path handle
the case where it is NULL.
Signed-off-by: Peter Maydell <address@hidden>
Reviewed-by: Eric Blake <address@hidden>
Signed-off-by: Stefan Hajnoczi <address@hidden>
Commit: 4e855baabfb548067b618808c32dc413d40e0bc7
https://github.com/qemu/qemu/commit/4e855baabfb548067b618808c32dc413d40e0bc7
Author: Benoît Canet <address@hidden>
Date: 2014-07-01 (Tue, 01 Jul 2014)
Changed paths:
M docs/qmp/qmp-events.txt
M qapi/event.json
Log Message:
-----------
qapi: Change back sector-count to sectors-count in quorum QAPI events.
fe069d9d had aligned code and documentation while dropping the s from the
actual JSON output. Fix that.
This also fix test/qemu-iotest/081 since the missing s was causing a
permutation.
Signed-off-by: Benoit Canet <address@hidden>
Reviewed-by: Eric Blake <address@hidden>
Signed-off-by: Stefan Hajnoczi <address@hidden>
Commit: fa40e65622352012dccd435147f28161375a6815
https://github.com/qemu/qemu/commit/fa40e65622352012dccd435147f28161375a6815
Author: Jeff Cody <address@hidden>
Date: 2014-07-01 (Tue, 01 Jul 2014)
Changed paths:
M blockdev.c
M qapi/block-core.json
M qmp-commands.hx
Log Message:
-----------
block: add QAPI command to allow live backing file change
This allows a user to make a live change to the backing file recorded in
an open image.
The image file to modify can be specified 2 ways:
1) image filename
2) image node-name
Note: this does not cause the backing file itself to be reopened; it
merely changes the backing filename in the image file structure, and
in internal BDS structures.
It is the responsibility of the user to pass a filename string that
can be resolved when the image chain is reopened, and the filename
string is not validated.
A good analogy for this command is that it is a live version of
'qemu-img rebase -u', with respect to changing the backing file string.
[Jeff is offline so I respun this patch in his absence. Dropped image
filename since using node-name is preferred and this is a new command.
No need to introduce the limitations of finding images by filename.
--Stefan]
Reviewed-by: Eric Blake <address@hidden>
Reviewed-by: Kevin Wolf <address@hidden>
Signed-off-by: Jeff Cody <address@hidden>
Signed-off-by: Stefan Hajnoczi <address@hidden>
Commit: 5a6684d2b957f9ec75d7ed7b14332293abec1d6c
https://github.com/qemu/qemu/commit/5a6684d2b957f9ec75d7ed7b14332293abec1d6c
Author: Jeff Cody <address@hidden>
Date: 2014-07-01 (Tue, 01 Jul 2014)
Changed paths:
M block.c
M include/block/block.h
Log Message:
-----------
block: add helper function to determine if a BDS is in a chain
This is a small helper function, to determine if 'base' is in the
chain of BlockDriverState 'top'. It returns true if it is in the chain,
and false otherwise.
If either argument is NULL, it will also return false.
Reviewed-by: Benoit Canet <address@hidden>
Reviewed-by: Eric Blake <address@hidden>
Signed-off-by: Jeff Cody <address@hidden>
Reviewed-by: Kevin Wolf <address@hidden>
Signed-off-by: Stefan Hajnoczi <address@hidden>
Commit: 54e269009099cdc9483be115f1e12d56ad459c5e
https://github.com/qemu/qemu/commit/54e269009099cdc9483be115f1e12d56ad459c5e
Author: Jeff Cody <address@hidden>
Date: 2014-07-01 (Tue, 01 Jul 2014)
Changed paths:
M block.c
M block/commit.c
M blockdev.c
M include/block/block.h
M include/block/block_int.h
M qapi/block-core.json
M qmp-commands.hx
Log Message:
-----------
block: extend block-commit to accept a string for the backing file
On some image chains, QEMU may not always be able to resolve the
filenames properly, when updating the backing file of an image
after a block commit.
For instance, certain relative pathnames may fail, or drives may
have been specified originally by file descriptor (e.g. /dev/fd/???),
or a relative protocol pathname may have been used.
In these instances, QEMU may lack the information to be able to make
the correct choice, but the user or management layer most likely does
have that knowledge.
With this extension to the block-commit api, the user is able to change
the backing file of the overlay image as part of the block-commit
operation.
This allows the change to be 'safe', in the sense that if the attempt
to write the overlay image metadata fails, then the block-commit
operation returns failure, without disrupting the guest.
If the commit top is the active layer, then specifying the backing
file string will be treated as an error (there is no overlay image
to modify in that case).
If a backing file string is not specified in the command, the backing
file string to use is determined in the same manner as it was
previously.
Reviewed-by: Eric Blake <address@hidden>
Signed-off-by: Jeff Cody <address@hidden>
Reviewed-by: Kevin Wolf <address@hidden>
Signed-off-by: Stefan Hajnoczi <address@hidden>
Commit: 13d8cc515dfcf5574077f964332d34890c0101d0
https://github.com/qemu/qemu/commit/13d8cc515dfcf5574077f964332d34890c0101d0
Author: Jeff Cody <address@hidden>
Date: 2014-07-01 (Tue, 01 Jul 2014)
Changed paths:
M block/stream.c
M blockdev.c
M hmp.c
M qapi/block-core.json
M qmp-commands.hx
Log Message:
-----------
block: add backing-file option to block-stream
On some image chains, QEMU may not always be able to resolve the
filenames properly, when updating the backing file of an image
after a block job.
For instance, certain relative pathnames may fail, or drives may
have been specified originally by file descriptor (e.g. /dev/fd/???),
or a relative protocol pathname may have been used.
In these instances, QEMU may lack the information to be able to make
the correct choice, but the user or management layer most likely does
have that knowledge.
With this extension to the block-stream api, the user is able to change
the backing file of the active layer as part of the block-stream
operation.
This allows the change to be 'safe', in the sense that if the attempt
to write the active image metadata fails, then the block-stream
operation returns failure, without disrupting the guest.
If a backing file string is not specified in the command, the backing
file string to use is determined in the same manner as it was
previously.
Reviewed-by: Eric Blake <address@hidden>
Signed-off-by: Jeff Cody <address@hidden>
Signed-off-by: Stefan Hajnoczi <address@hidden>
Commit: 8593efa4fb33b8c1f3e3af04f771d8376ae61092
https://github.com/qemu/qemu/commit/8593efa4fb33b8c1f3e3af04f771d8376ae61092
Author: Peter Maydell <address@hidden>
Date: 2014-07-01 (Tue, 01 Jul 2014)
Changed paths:
M block.c
M block/commit.c
M block/cow.c
M block/qed.c
M block/raw-posix.c
M block/stream.c
M block/vdi.c
M block/vmdk.c
M block/vpc.c
M blockdev.c
M docs/qmp/qmp-events.txt
M hmp.c
M hw/block/dataplane/virtio-blk.c
M hw/block/virtio-blk.c
M hw/core/qdev-properties-system.c
M hw/core/qdev.c
M hw/s390x/s390-virtio-bus.c
M hw/s390x/s390-virtio-bus.h
M hw/s390x/virtio-ccw.c
M hw/s390x/virtio-ccw.h
M hw/virtio/virtio-pci.c
M hw/virtio/virtio-pci.h
M include/block/block.h
M include/block/block_int.h
M include/hw/qdev-properties.h
M include/hw/virtio/virtio-blk.h
M qapi/block-core.json
M qapi/event.json
M qemu-doc.texi
M qemu-img.texi
M qmp-commands.hx
M tests/qemu-iotests-quick.sh
M tests/qemu-iotests/040
M tests/qemu-iotests/082.out
M tests/qemu-iotests/group
Log Message:
-----------
Merge remote-tracking branch 'remotes/stefanha/tags/block-pull-request' into
staging
Block pull request
# gpg: Signature made Tue 01 Jul 2014 09:47:15 BST using RSA key ID 81AB73C8
# gpg: Good signature from "Stefan Hajnoczi <address@hidden>"
# gpg: aka "Stefan Hajnoczi <address@hidden>"
* remotes/stefanha/tags/block-pull-request: (23 commits)
block: add backing-file option to block-stream
block: extend block-commit to accept a string for the backing file
block: add helper function to determine if a BDS is in a chain
block: add QAPI command to allow live backing file change
qapi: Change back sector-count to sectors-count in quorum QAPI events.
block/cow: Avoid use of uninitialized cow_bs in error path
block: simplify bdrv_find_base() and bdrv_find_overlay()
block: make 'top' argument to block-commit optional
iotests: Add more tests to quick group
iotests: Add qemu tests to quick group
iotests: Simplify qemu-iotests-quick.sh
qemu-img create: add 'nocow' option
virtio-blk: remove need for explicit x-data-plane=on option
qdev: drop iothread property type
virtio-blk: replace x-iothread with iothread link property
virtio-blk: move qdev properties into virtio-blk.c
virtio: fix virtio-blk child refcount in transports
virtio-blk: drop virtio_blk_set_conf()
virtio-blk: use aliases instead of duplicate qdev properties
qdev: add qdev_alias_all_properties()
...
Signed-off-by: Peter Maydell <address@hidden>
Compare: https://github.com/qemu/qemu/compare/c26f3a0a6dfe...8593efa4fb33
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Qemu-commits] [qemu/qemu] dc80ca: virtio-blk: avoid qdev property definition duplica...,
GitHub <=