aboutsummaryrefslogtreecommitdiff
path: root/scripts/qapi/expr.py
diff options
context:
space:
mode:
authorPeter Xu <peterx@redhat.com>2025-06-13 10:07:52 -0400
committerFabiano Rosas <farosas@suse.de>2025-07-11 10:37:35 -0300
commit2862d6d4fb09f57cabc4389fed34ae767ab2da94 (patch)
treeedb3e9a4634bd6a3a7ef738617de5e2d3d561ec3 /scripts/qapi/expr.py
parent31a90360fd8209fb479964a37c4329d5dbc3fb07 (diff)
downloadqemu-2862d6d4fb09f57cabc4389fed34ae767ab2da94.zip
qemu-2862d6d4fb09f57cabc4389fed34ae767ab2da94.tar.gz
qemu-2862d6d4fb09f57cabc4389fed34ae767ab2da94.tar.bz2
migration/hmp: Fix postcopy-blocktime per-vCPU results
Unfortunately, it was never correctly shown.. This is only found when I started to look into making the blocktime feature more useful (so as to avoid using bpftrace, even though I'm not sure which one will be harder to use..). So the old dump would look like this: Postcopy vCPU Blocktime: 0-1,4,10,21,33,46,48,59 Even though there're actually 40 vcpus, and the string will merge same elements and also sort them. To fix it, simply loop over the uint32List manually. Now it looks like: Postcopy vCPU Blocktime (ms): [15, 0, 0, 43, 29, 34, 36, 29, 37, 41, 33, 37, 45, 52, 50, 38, 40, 37, 40, 49, 40, 35, 35, 35, 81, 19, 18, 19, 18, 30, 22, 3, 0, 0, 0, 0, 0, 0, 0, 0] Cc: Dr. David Alan Gilbert <dave@treblig.org> Cc: Alexey Perevalov <a.perevalov@samsung.com> Cc: Markus Armbruster <armbru@redhat.com> Tested-by: Mario Casquero <mcasquer@redhat.com> Reviewed-by: Juraj Marcin <jmarcin@redhat.com> Reviewed-by: Fabiano Rosas <farosas@suse.de> Link: https://lore.kernel.org/r/20250613140801.474264-3-peterx@redhat.com Signed-off-by: Peter Xu <peterx@redhat.com> Signed-off-by: Fabiano Rosas <farosas@suse.de>
Diffstat (limited to 'scripts/qapi/expr.py')
0 files changed, 0 insertions, 0 deletions