[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <8617698e-0d1a-15d8-7e6d-e63408857b1c@de.ibm.com>
Date: Tue, 26 Jun 2018 10:54:41 +0200
From: Christian Borntraeger <borntraeger@...ibm.com>
To: Cornelia Huck <cohuck@...hat.com>
Cc: Guenter Roeck <linux@...ck-us.net>,
Martin Schwidefsky <schwidefsky@...ibm.com>,
Vasily Gorbik <gor@...ux.ibm.com>,
Heiko Carstens <heiko.carstens@...ibm.com>,
linux-s390@...r.kernel.org, linux-kernel@...r.kernel.org,
qemu-s390x <qemu-s390x@...gnu.org>,
qemu-devel <qemu-devel@...gnu.org>,
Thomas Huth <thuth@...hat.com>
Subject: Re: s390 qemu boot failure in -next
On 06/26/2018 10:29 AM, Cornelia Huck wrote:
[...]
>>>>
>>>> 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 think we can drop this patch for now.
>
> I'll go ahead and queue Thomas' fix, though.
yes, please
Powered by blists - more mailing lists