summaryrefslogtreecommitdiffstats
path: root/docs/tools/qemu-trace-stap.rst
diff options
context:
space:
mode:
authorEric Blake2020-10-27 06:05:55 +0100
committerEric Blake2020-10-30 21:22:00 +0100
commitdbc7b01492371e4a54b92d2b6d968f9b863cc794 (patch)
tree24812091f95b86d03192a23bec70e21d9a5b74eb /docs/tools/qemu-trace-stap.rst
parentnbd: Add new qemu:allocation-depth metadata context (diff)
downloadqemu-dbc7b01492371e4a54b92d2b6d968f9b863cc794.tar.gz
qemu-dbc7b01492371e4a54b92d2b6d968f9b863cc794.tar.xz
qemu-dbc7b01492371e4a54b92d2b6d968f9b863cc794.zip
nbd: Add 'qemu-nbd -A' to expose allocation depth
Allow the server to expose an additional metacontext to be requested by savvy clients. qemu-nbd adds a new option -A to expose the qemu:allocation-depth metacontext through NBD_CMD_BLOCK_STATUS; this can also be set via QMP when using block-export-add. qemu as client is hacked into viewing the key aspects of this new context by abusing the already-experimental x-dirty-bitmap option to collapse all depths greater than 2, which results in a tri-state value visible in the output of 'qemu-img map --output=json' (yes, that means x-dirty-bitmap is now a bit of a misnomer, but I didn't feel like renaming it as it would introduce a needless break of back-compat, even though we make no compat guarantees with x- members): unallocated (depth 0) => "zero":false, "data":true local (depth 1) => "zero":false, "data":false backing (depth 2+) => "zero":true, "data":true libnbd as client is probably a nicer way to get at the information without having to decipher such hacks in qemu as client. ;) Signed-off-by: Eric Blake <eblake@redhat.com> Message-Id: <20201027050556.269064-11-eblake@redhat.com> Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Diffstat (limited to 'docs/tools/qemu-trace-stap.rst')
0 files changed, 0 insertions, 0 deletions