From: Thomas Huth <thuth@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: "Jason J. Herne" <jjherne@linux.ibm.com>,
qemu-s390x <qemu-s390x@nongnu.org>,
Cornelia Huck <cohuck@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Janosch Frank <frankja@linux.ibm.com>
Subject: Re: [PATCH] s390-bios: Skip writing iplb location to low core for ccw ipl
Date: Tue, 3 Nov 2020 13:32:47 +0100 [thread overview]
Message-ID: <8e5e3e03-f25b-4d69-a2bd-42c46a675c04@redhat.com> (raw)
In-Reply-To: <20201030122823.347140-1-borntraeger@de.ibm.com>
On 30/10/2020 13.28, Christian Borntraeger wrote:
> From: "Jason J. Herne" <jjherne@linux.ibm.com>
>
> The architecture states that the iplb location is only written to low
> core for list directed ipl and not for traditional ccw ipl. If we don't
> skip this then operating systems that load by reading into low core
> memory may fail to start.
Just double-checking: But doing write_subsystem_identification()
unconditionally is ok, right?
> We should also not write the iplb pointer for network boot as it might
> overwrite content that we got via network.
FWIW, write_iplb_location() is already just a dummy function in netmain.c,
so this should not have been an issue in the network bootloader, I hope.
> Signed-off-by: Jason J. Herne <jjherne@linux.ibm.com>
> Fixes: 9bfc04f9ef68 ("pc-bios: s390x: Save iplb location in lowcore")
> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
> ---
> pc-bios/s390-ccw/main.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/pc-bios/s390-ccw/main.c b/pc-bios/s390-ccw/main.c
> index 43c792cf9509..fc4bfaa45529 100644
> --- a/pc-bios/s390-ccw/main.c
> +++ b/pc-bios/s390-ccw/main.c
> @@ -43,7 +43,9 @@ void write_subsystem_identification(void)
>
> void write_iplb_location(void)
> {
> - lowcore->ptr_iplb = ptr2u32(&iplb);
> + if (cutype == CU_TYPE_VIRTIO && virtio_get_device_type() != VIRTIO_ID_NET) {
> + lowcore->ptr_iplb = ptr2u32(&iplb);
> + }
> }
Acked-by: Thomas Huth <thuth@redhat.com>
Christian, Cornelia, could you please pick up the patch? I'm not sure
whether I can do another PR this week for the RC...
next prev parent reply other threads:[~2020-11-03 12:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 12:28 [PATCH] s390-bios: Skip writing iplb location to low core for ccw ipl Christian Borntraeger
2020-11-03 12:08 ` Christian Borntraeger
2020-11-03 12:32 ` Thomas Huth [this message]
2020-11-03 12:35 ` Cornelia Huck
2020-11-03 17:15 ` Christian Borntraeger
2020-11-04 12:22 ` Cornelia Huck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8e5e3e03-f25b-4d69-a2bd-42c46a675c04@redhat.com \
--to=thuth@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=jjherne@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).