qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Vasily Gorbik <gor@linux.ibm.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
	Cornelia Huck <cohuck@redhat.com>,
	Guenter Roeck <linux@roeck-us.net>,
	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: Mon, 25 Jun 2018 17:09:17 +0200	[thread overview]
Message-ID: <cover.thread-8b0da3.your-ad-here.call-01529937119-ext-3705@work.hours> (raw)
In-Reply-To: <64bcba64-b88f-3594-da6e-7c2118482c20@roeck-us.net>

On Mon, Jun 25, 2018 at 06:35:30AM -0700, Guenter Roeck wrote:
> On 06/25/2018 05:26 AM, Christian Borntraeger wrote:
> > 
> > 
> > On 06/25/2018 10:49 AM, Cornelia Huck wrote:
> > > On Mon, 25 Jun 2018 10:36:33 +0200
> > > Vasily Gorbik <gor@linux.ibm.com> wrote:
> > > 
> > > > This change has been done on purpose. Uncompressed image is not going
> > > > to be bootable any more. In future the decompressor phase would get
> > > > more function (early memory detection as an example) and there is no
> > > > chance to duplicate that code in uncompressed image as well (to keep it
> > > > bootable on its own). The patch series commit messages contain more
> > > > technical details.
> > > > 
> > > > For qemu either bzImage or arch/s390/boot/compressed/vmlinux should be
> > > > used, which are bootable images.
> > > > 
> > > > But that's really confusing that uncompressed vmlinux is still kind
> > > > of booting. May be we should discuss how to avoid this confusion
> > > > (may be change uncompressed image enty point to a function doing
> > > > disabled wait with badb007 or smth) and how to encourage people to use
> > > > arch/s390/boot/compressed/vmlinux instead.
> > > 
> 
> If an image is not expected to be bootable, a message such as "This image does
> not boot. Please use <correct image>" would be nice. Unfortunately, which image
> to boot under qemu is pretty much undocumented, and it is guesswork for each
> architecture/platform.
> 
> Guenter
> 
> > I talked to Vasily and the vmlinux file in the linux source path is just an
> > intermediate file. Future changes will happen that will make that ELF file
> > unsuitable for direct boot anyway (e.g. think about potential ASLR or Kasan
> > changes).
> > 
> >   If yes, it would make sense to explicitly fence it. But I'm
> > > worried that it would break previously working setups (did we document
> > > the purpose of the images anywhere?
> > > 

To avoid confusion with trying to boot uncompressed vmlinux under qemu
we could detect it and print "nice" message in the kernel.

Please consider the following patch.

Vasily Gorbik (1):
  s390/boot: block uncompressed vmlinux booting attempts

 arch/s390/boot/head.S         |  4 ++--
 arch/s390/include/asm/setup.h |  3 ++-
 arch/s390/kernel/early.c      | 12 ++++++++++++
 3 files changed, 16 insertions(+), 3 deletions(-)

-- 
⣔⢻⣟⢢ 2.18.0.rc2.13.g4da9a5d
⣿⢿⡿⣿ pacman edition

  reply	other threads:[~2018-06-25 15:09 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
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 [this message]
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=cover.thread-8b0da3.your-ad-here.call-01529937119-ext-3705@work.hours \
    --to=gor@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.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).