| commit | 962982329029acb6651f81b47cb401e593bb62df | |
| author | Christian Borntraeger <borntraeger@de.ibm.com> | |
| Wed, 18 Jun 2014 12:16:45 +0000 (18 14:16 +0200) | ||
| committer | Cornelia Huck <cornelia.huck@de.ibm.com> | |
| Mon, 23 Jun 2014 12:03:31 +0000 (23 14:03 +0200) | ||
| tree | 66a73474911ffafac83a666f89735ec0efd2714b | treesnapshot (tar.gz zip) |
| parent | 554f80896dbdc6ce5bb01eab9659facf05ccf168 | commitdiff |
pc-bios/s390-ccw: do a subsystem reset before running the guest
The loader BIOS has already activated several devices. Let's do a
subsystem reset before jumping into the guest. As there is no direct
way of doing so, we use diagnose 308 to bring the system in a
defined state. This is similar to what kdump on s390 uses. We have
to define a small trampoline function that restores the low bytes
to whatever the bootmap has written there.
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by: Jens Freimann <jfrei@linux.vnet.ibm.com>
Reviewed-by: Alexander Graf <agraf@suse.de>
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
The loader BIOS has already activated several devices. Let's do a
subsystem reset before jumping into the guest. As there is no direct
way of doing so, we use diagnose 308 to bring the system in a
defined state. This is similar to what kdump on s390 uses. We have
to define a small trampoline function that restores the low bytes
to whatever the bootmap has written there.
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by: Jens Freimann <jfrei@linux.vnet.ibm.com>
Reviewed-by: Alexander Graf <agraf@suse.de>
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
| pc-bios/s390-ccw/bootmap.c | diffblobblamehistory |