pc-bios: s390x: Save iplb location in lowcore
commit9bfc04f9ef6802fff0fc77130ff345a541783363
authorJanosch Frank <frankja@linux.ibm.com>
Wed, 4 Mar 2020 11:42:31 +0000 (4 06:42 -0500)
committerChristian Borntraeger <borntraeger@de.ibm.com>
Tue, 10 Mar 2020 09:18:08 +0000 (10 10:18 +0100)
tree9b2f341150b32aa7eaa1fc775974b879e8fb1474
parent373c7068dd610e97f0b551b5a6d0a27cd6da4506
pc-bios: s390x: Save iplb location in lowcore

The POP states that for a list directed IPL the IPLB is stored into
memory by the machine loader and its address is stored at offset 0x14
of the lowcore.

ZIPL currently uses the address in offset 0x14 to access the IPLB and
acquire flags about secure boot. If the IPLB address points into
memory which has an unsupported mix of flags set, ZIPL will panic
instead of booting the OS.

As the lowcore can have quite a high entropy for a guest that did drop
out of protected mode (i.e. rebooted) we encountered the ZIPL panic
quite often.

Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
Tested-by: Marc Hartmayer <mhartmay@linux.ibm.com>
Message-Id: <20200304114231.23493-19-frankja@linux.ibm.com>
Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com>
Reviewed-by: David Hildenbrand <david@redhat.com>
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
pc-bios/s390-ccw/jump2ipl.c
pc-bios/s390-ccw/main.c
pc-bios/s390-ccw/netmain.c
pc-bios/s390-ccw/s390-arch.h
pc-bios/s390-ccw/s390-ccw.h