Skip to contentSkip to conversation

qmp: Documentation for BLOCK_IMAGE_CORRUPTED

PATCH Applied Max Reitz 3 participants 3 messages Sep 3, 2013 – Sep 4, 2013

lore
Share & tools
lore

Max Reitz

author
#0 lore raw

PATCH v2 1/1 qmp: Documentation for BLOCK_IMAGE_CORRUPTED

Add an appropriate entry describing this event and its parameters into qmp-events.txt.

---
v2:
- moved section to keep qmp-events.txt sorted

---
 QMP/qmp-events.txt | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)
QMP/qmp-events.txt +22 -0
index 39b6016..4b24ec9 100644
@@ -18,6 +18,28 @@ Example:
     "data": { "actual": 944766976 },
     "timestamp": { "seconds": 1267020223, "microseconds": 435656 } }
 
+BLOCK_IMAGE_CORRUPTED
+---------------------
+
+Emitted when a disk image is being marked corrupt.
+
+Data:
+
+- "device": Device name (json-string)
+- "msg":    Informative message (e.g., reason for the corruption) (json-string)
+- "offset": If the corruption resulted from an image access, this is the access
+            offset into the image (json-int)
+- "size":   If the corruption resulted from an image access, this is the access
+            size (json-int)
+
+Example:
+
+{ "event": "BLOCK_IMAGE_CORRUPTED",
+    "data": { "device": "ide0-hd0",
+        "msg": "Prevented active L1 table overwrite", "offset": 196608,
+        "size": 65536 },
+    "timestamp": { "seconds": 1378126126, "microseconds": 966463 } }
+
 BLOCK_IO_ERROR
 --------------
 
Signature · 1 line
1.8.3.1
Reviewed-by on v2 1/1
#1 lore raw

Am 03.09.2013 um 15:49 hat Max Reitz geschrieben:

Quoted 8 lines

Add an appropriate entry describing this event and its parameters into qmp-events.txt.

---
v2:
- moved section to keep qmp-events.txt sorted

Don't forget to keep both Stefan and me CCed for block layer patches. This week Stefan handles the queue.

Kevin

Quoted 40 lines
 QMP/qmp-events.txt | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)
QMP/qmp-events.txt +22 -0
index 39b6016..4b24ec9 100644
@@ -18,6 +18,28 @@ Example:
     "data": { "actual": 944766976 },
     "timestamp": { "seconds": 1267020223, "microseconds": 435656 } }
 
+BLOCK_IMAGE_CORRUPTED
+---------------------
+
+Emitted when a disk image is being marked corrupt.
+
+Data:
+
+- "device": Device name (json-string)
+- "msg":    Informative message (e.g., reason for the corruption) (json-string)
+- "offset": If the corruption resulted from an image access, this is the access
+            offset into the image (json-int)
+- "size":   If the corruption resulted from an image access, this is the access
+            size (json-int)
+
+Example:
+
+{ "event": "BLOCK_IMAGE_CORRUPTED",
+    "data": { "device": "ide0-hd0",
+        "msg": "Prevented active L1 table overwrite", "offset": 196608,
+        "size": 65536 },
+    "timestamp": { "seconds": 1378126126, "microseconds": 966463 } }
+
 BLOCK_IO_ERROR
 --------------
 
Signature · 1 line
1.8.3.1
#2 lore raw
In reply to Max Reitz
Quoted 11 lines · Max Reitz

Add an appropriate entry describing this event and its parameters into qmp-events.txt.

---
v2:
- moved section to keep qmp-events.txt sorted

---
 QMP/qmp-events.txt | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block

Stefan