From: Greg Kurz <groug@kaod.org>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: David Gibson <david@gibson.dropbear.id.au>,
Laurent Vivier <lvivier@redhat.com>,
Andrew Jones <drjones@redhat.com>,
qemu-ppc@nongnu.org,
Thomas Huth <thuth@redhat.com>"Richard W.M. Jones"
<rjones@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH RFC] spapr: by-pass SLOF when -kernel is provided
Date: Wed, 6 Jul 2016 09:04:30 +0200 [thread overview]
Message-ID: <20160706090430.2c8d5ef3@bahia.lan> (raw)
In-Reply-To: <ce94508f-64d1-a75b-944a-b3cdae3f75c3@ozlabs.ru>
[-- Attachment #1: Type: text/plain, Size: 1706 bytes --]
On Wed, 6 Jul 2016 13:33:49 +1000
Alexey Kardashevskiy <aik@ozlabs.ru> wrote:
> On 06/07/16 11:35, David Gibson wrote:
> > On Tue, Jul 05, 2016 at 04:42:37PM +0200, Laurent Vivier wrote:
> >> As device-tree is now fully built by QEMU, we don't need SLOF
> >> anymore if the kernel is provided on the command line.
> >>
> >> In this case, don't load SLOF and boot directly into the
> >> kernel.
> >>
> >> This saves at least 5 seconds on the boot sequence.
> >>
> >> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
> >
> > I'm not comfortable applying this. We actually used to do this ages
> > ago, but changed to always running through SLOF, and there were
> > reasons for doing so.
> >
> > I don't remember exactly what they were, but I think it boiled down to
> > slight differences in state between booting from SLOF and booting
> > without SLOF leading to confusing errors from the guest kernel.
> >
>
> PCI resource allocation is still done by SLOF (however having them not set
> will trigger allocation in the guest but this is rather unexpected
> workaround than a feature); "client-architecture-support" won't work
> without SLOF either (i.e. compatibile PowerISA 2.0x CPUs).
>
Not even sure the workaround actually works:
I retried with a ppc64le guest and this time I get:
[ 1.055922] virtio-pci 0000:00:01.0: virtio_pci: leaving for legacy driver
[ 1.056048] virtio-pci: probe of 0000:00:01.0 failed with error -12
[ 1.056263] virtio-pci 0000:00:00.0: virtio_pci: leaving for legacy driver
[ 1.056373] virtio-pci: probe of 0000:00:00.0 failed with error -12
i.e. virtio_reset() isn't called during probing :-\
--
Greg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-07-06 7:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 14:42 [Qemu-devel] [PATCH RFC] spapr: by-pass SLOF when -kernel is provided Laurent Vivier
2016-07-05 17:58 ` [Qemu-devel] [Qemu-ppc] " Cédric Le Goater
2016-07-05 18:44 ` Greg Kurz
2016-07-05 18:51 ` Laurent Vivier
2016-07-06 7:03 ` Greg Kurz
2016-07-06 8:37 ` Laurent Vivier
2016-07-06 1:35 ` [Qemu-devel] " David Gibson
2016-07-06 3:33 ` Alexey Kardashevskiy
2016-07-06 7:04 ` Greg Kurz [this message]
2016-07-06 8:02 ` [Qemu-devel] [Qemu-ppc] " Nikunj A Dadhania
2016-07-06 8:04 ` Alexey Kardashevskiy
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=20160706090430.2c8d5ef3@bahia.lan \
--to=groug@kaod.org \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=drjones@redhat.com \
--cc=lvivier@redhat.com \
--cc=qemu-ppc@nongnu.org \
--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).