summaryrefslogtreecommitdiffstats
path: root/trace-events
diff options
context:
space:
mode:
authorEric Blake2017-05-15 23:41:12 +0200
committerMarkus Armbruster2017-05-23 13:28:17 +0200
commit802f045a5f61b781df55e4492d896b4d20503ba7 (patch)
tree69a69ba0835eb19dfa9d4f06944ed09def8d2e20 /trace-events
parentshutdown: Prepare for use of an enum in reset/shutdown_request (diff)
downloadqemu-802f045a5f61b781df55e4492d896b4d20503ba7.tar.gz
qemu-802f045a5f61b781df55e4492d896b4d20503ba7.tar.xz
qemu-802f045a5f61b781df55e4492d896b4d20503ba7.zip
shutdown: Preserve shutdown cause through replay
With the recent addition of ShutdownCause, we want to be able to pass a cause through any shutdown request, and then faithfully replay that cause when later replaying the same sequence. The easiest way is to expand the reply event mechanism to track a series of values for EVENT_SHUTDOWN, one corresponding to each value of ShutdownCause. We are free to change the replay stream as needed, since there are already no guarantees about being able to use a replay stream by any other version of qemu than the one that generated it. The cause is not actually fed back until the next patch changes the signature for requesting a shutdown; a TODO marks that upcoming change. Yes, this uses the gcc/clang extension of a ranged case label, but this is not the first time we've used non-C99 constructs. Signed-off-by: Eric Blake <eblake@redhat.com> Reviewed-by: Pavel Dovgalyuk <pavel.dovgaluk@ispras.ru> Message-Id: <20170515214114.15442-4-eblake@redhat.com> Reviewed-by: Markus Armbruster <armbru@redhat.com> Signed-off-by: Markus Armbruster <armbru@redhat.com>
Diffstat (limited to 'trace-events')
0 files changed, 0 insertions, 0 deletions