| commit | c27c73aaf924655b2cc2e74384a639805acededb | |
| author | John Snow <jsnow@redhat.com> | |
| Mon, 23 Feb 2015 16:18:05 +0000 (23 11:18 -0500) | ||
| committer | Kevin Wolf <kwolf@redhat.com> | |
| Tue, 10 Mar 2015 13:02:23 +0000 (10 14:02 +0100) | ||
| tree | 65076713068cc1c0f9f3e1bef76caa8cbc821a8a | treesnapshot (tar.gz zip) |
| parent | e8ef87433ee005d304ba19c56488474432eb0c53 | commitdiff |
ahci: Recompute cur_cmd on migrate post load
When the AHCI HBA device is migrated, all of the information that
led to the request being created is stored in the AHCIDevice
structures, except for pointers into guest data where return
information needs to be stored.
The "cur_cmd" field is usually responsible for this.
To rebuild the cur_cmd pointer post-migration, we can utilize
the busy_slot index to figure out where the command header
we are still processing is.
This allows a machine in a halted state from rerror=stop or
werror=stop to be migrated and resume operations without issue.
Signed-off-by: John Snow <jsnow@redhat.com>
Message-id: 1424708286-16483-17-git-send-email-jsnow@redhat.com
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
When the AHCI HBA device is migrated, all of the information that
led to the request being created is stored in the AHCIDevice
structures, except for pointers into guest data where return
information needs to be stored.
The "cur_cmd" field is usually responsible for this.
To rebuild the cur_cmd pointer post-migration, we can utilize
the busy_slot index to figure out where the command header
we are still processing is.
This allows a machine in a halted state from rerror=stop or
werror=stop to be migrated and resume operations without issue.
Signed-off-by: John Snow <jsnow@redhat.com>
Message-id: 1424708286-16483-17-git-send-email-jsnow@redhat.com
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
| hw/ide/ahci.c | diffblobblamehistory |