Searched hist:"8 b9b0cc2fd1b866c0ce6c7f7385d840aad8b4c2c" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/qemu/block/ |
| H A D | blkdebug.c | diff 8b9b0cc2fd1b866c0ce6c7f7385d840aad8b4c2c Mon Mar 15 11:27:00 CDT 2010 Kevin Wolf <kwolf@redhat.com> blkdebug: Add events and rules
Block drivers can trigger a blkdebug event whenever they reach a place where it
could be useful to inject an error for testing/debugging purposes.
Rules are read from a blkdebug config file and describe which action is taken
when an event is triggered. For now this is only injecting an error (with a few
options) or changing the state (which is an integer). Rules can be declared to
be active only in a specific state; this way later rules can distiguish on
which path we came to trigger their event.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
|
| /openbmc/qemu/ |
| H A D | block.c | diff 8b9b0cc2fd1b866c0ce6c7f7385d840aad8b4c2c Mon Mar 15 11:27:00 CDT 2010 Kevin Wolf <kwolf@redhat.com> blkdebug: Add events and rules
Block drivers can trigger a blkdebug event whenever they reach a place where it
could be useful to inject an error for testing/debugging purposes.
Rules are read from a blkdebug config file and describe which action is taken
when an event is triggered. For now this is only injecting an error (with a few
options) or changing the state (which is an integer). Rules can be declared to
be active only in a specific state; this way later rules can distiguish on
which path we came to trigger their event.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
|