summary refs log tree commit diff stats
path: root/results/classifier/105/semantic/1338957
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-06-03 12:04:13 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-06-03 12:04:13 +0000
commit256709d2eb3fd80d768a99964be5caa61effa2a0 (patch)
tree05b2352fba70923126836a64b6a0de43902e976a /results/classifier/105/semantic/1338957
parent2ab14fa96a6c5484b5e4ba8337551bb8dcc79cc5 (diff)
downloademulator-bug-study-256709d2eb3fd80d768a99964be5caa61effa2a0.tar.gz
emulator-bug-study-256709d2eb3fd80d768a99964be5caa61effa2a0.zip
add new classifier result
Diffstat (limited to 'results/classifier/105/semantic/1338957')
-rw-r--r--results/classifier/105/semantic/133895731
1 files changed, 31 insertions, 0 deletions
diff --git a/results/classifier/105/semantic/1338957 b/results/classifier/105/semantic/1338957
new file mode 100644
index 00000000..2d86d0c7
--- /dev/null
+++ b/results/classifier/105/semantic/1338957
@@ -0,0 +1,31 @@
+semantic: 0.689
+graphic: 0.680
+instruction: 0.663
+device: 0.640
+socket: 0.515
+network: 0.493
+mistranslation: 0.477
+vnc: 0.475
+boot: 0.459
+other: 0.320
+KVM: 0.241
+assembly: 0.231
+
+RFE: add an event to report block devices watermark
+
+Add an event to report if a block device usage exceeds a threshold. The threshold should be configurable with a monitor command. The event should report the affected block device. Additional useful information could be the offset of the highest sector , like in the query-blockstats output.
+
+Rationale for the RFE
+Managing applications, like oVirt (http://www.ovirt.org), make extensive use of thin-provisioned disk images.
+In order to let the guest run flawlessly and be not unnecessarily paused, oVirt sets a watermark and automatically resized the image once the watermark is reached or exceeded.
+
+In order to detect the mark crossing, the managing application has no choice than aggressively polling the QEMU monitor
+using the query-blockstats command. This lead to unnecessary system load, and is made even worse under scale: scenarios
+with hunderds of VM are becoming not unusual.
+
+patch posted on qemu-devel, reviewd, acked and merged into maintainer's branch:
+https://github.com/stefanha/qemu/commit/f050ea639522e9dd7e501ef285a2a12709b8726a
+
+Upstream here:
+https://git.qemu.org/?p=qemu.git;a=commitdiff;h=e2462113b2003085ad16f15e1
+