From: Cornelia Huck <cohuck@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
qemu-s390x <qemu-s390x@nongnu.org>,
qemu-devel <qemu-devel@nongnu.org>,
Thomas Huth <thuth@redhat.com>
Subject: Re: [Qemu-devel] s390 qemu boot failure in -next
Date: Tue, 26 Jun 2018 10:29:54 +0200 [thread overview]
Message-ID: <20180626102954.73965b42.cohuck@redhat.com> (raw)
In-Reply-To: <d56829a3-fecf-b812-d002-8ee22ae08da2@de.ibm.com>
On Mon, 25 Jun 2018 10:29:46 +0200
Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> On 06/25/2018 10:05 AM, Cornelia Huck wrote:
> > On Mon, 25 Jun 2018 09:27:59 +0200
> > Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> >> Something like this in QEMU
> >>
> >> diff --git a/hw/s390x/ipl.c b/hw/s390x/ipl.c
> >> index f278036fa7..14153ce880 100644
> >> --- a/hw/s390x/ipl.c
> >> +++ b/hw/s390x/ipl.c
> >> @@ -187,11 +187,13 @@ static void s390_ipl_realize(DeviceState *dev, Error **errp)
> >> */
> >> if (pentry == KERN_IMAGE_START || pentry == 0x800) {
> >> ipl->start_addr = KERN_IMAGE_START;
> >> - /* Overwrite parameters in the kernel image, which are "rom" */
> >> - strcpy(rom_ptr(KERN_PARM_AREA), ipl->cmdline);
> >> } else {
> >> ipl->start_addr = pentry;
> >> }
> >> + if (ipl->cmdline) {
> >> + /* If there is a command line, put it in the right place */
> >> + strcpy(rom_ptr(KERN_PARM_AREA), ipl->cmdline);
> >> + }
> >
> > Check for the magic Linux string (like in the non-elf case) first?
>
> Even that does not exists in vmlinux but only in bzImage with the latest patchset
> (in next, but not upstream yet)
Ok.
> >
> >>
> >> if (ipl->initrd) {
> >> ram_addr_t initrd_offset;
> >>
> >> would put the command line in no matter what the start address is.
> >
> > I'm for putting that one in (and backporting it to qemu-stable). It's a
> > bit worrying, though, that our ipl code is so fragile...
>
> We actually have to combine this with Thomas fix (to check for rom_ptr returning
> something sane). It seems that ipl->commandline is always there, so we have to
> check for strlen!=0 it seems..
>
> I mean if somebody ask for "-append something" we can certainly always write something
> if there is rom/ram.
Given that the uncompressed image is not supposed to be bootable
anymore, does it make sense to add this anyway?
I'll go ahead and queue Thomas' fix, though.
next prev parent reply other threads:[~2018-06-26 8:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180622194736.GA5794@roeck-us.net>
[not found] ` <126ac556-0602-b927-58f5-cb5f65a5e0ec@de.ibm.com>
2018-06-25 7:27 ` [Qemu-devel] s390 qemu boot failure in -next Christian Borntraeger
2018-06-25 8:02 ` [Qemu-devel] [qemu-s390x] " Christian Borntraeger
2018-06-25 8:08 ` Cornelia Huck
2018-06-25 8:27 ` Thomas Huth
2018-06-25 8:05 ` [Qemu-devel] " Cornelia Huck
2018-06-25 8:29 ` Christian Borntraeger
2018-06-26 8:29 ` Cornelia Huck [this message]
2018-06-26 8:54 ` Christian Borntraeger
2018-06-25 8:36 ` Vasily Gorbik
2018-06-25 8:49 ` Cornelia Huck
2018-06-25 12:26 ` Christian Borntraeger
2018-06-25 13:35 ` Guenter Roeck
2018-06-25 15:09 ` Vasily Gorbik
2018-06-25 15:09 ` [Qemu-devel] [PATCH] s390/boot: block uncompressed vmlinux booting attempts Vasily Gorbik
2018-06-25 19:40 ` Guenter Roeck
2018-06-26 7:30 ` Christian Borntraeger
2018-06-26 8:24 ` Cornelia Huck
2018-06-26 5:32 ` [Qemu-devel] s390 qemu boot failure in -next Georgi Guninski
2018-06-26 5:40 ` Thomas Huth
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=20180626102954.73965b42.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=gor@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=schwidefsky@de.ibm.com \
--cc=thuth@redhat.com \
/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).