tree d2730ee2e84d06a24048e8d1abbe937207b60824
parent 9e2a3701a1fcfec0316b9dc1a6cd62869de5542c
author Kevin Wolf <kwolf@redhat.com> 1306414834 +0200
committer Kevin Wolf <kwolf@redhat.com> 1308141375 +0200

ide: Split error status from status register

When adding the werror=stop mode, some flags were added to s->status
which are used to determine what kind of operation should be restarted
when the VM is continued.

Unfortunately, it turns out that s->status is in fact a device register
and as such is visible to the guest (some of the abused bits are even
writable for the guest).

For migration we keep on using the old VMState field (renamed to
migration_compat_status) if the status register doesn't use any of the
previously abused bits. If it does, we use a subsection with a clean copy of
the status register.

The error status is always sent in a subsection if there is any error. It can't
use the old field because errors happen even without PCI.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>