From: David Gibson <david@gibson.dropbear.id.au>
To: Greg Kurz <groug@kaod.org>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-ppc] [GIT PULL for qemu-pseries] spapr: Render full FDT on ibm, client-architecture-support
Date: Thu, 29 Aug 2019 10:00:22 +1000 [thread overview]
Message-ID: <20190829000022.GD16342@umbus.fritz.box> (raw)
In-Reply-To: <20190828115014.0364baa1@bahia.lab.toulouse-stg.fr.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 2380 bytes --]
On Wed, Aug 28, 2019 at 11:50:14AM +0200, Greg Kurz wrote:
> On Wed, 28 Aug 2019 15:57:40 +1000
> David Gibson <david@gibson.dropbear.id.au> wrote:
>
> > On Wed, Aug 28, 2019 at 01:27:35PM +1000, Alexey Kardashevskiy wrote:
> > >
> > >
> > > On 28/08/2019 12:12, David Gibson wrote:
> > > > On Wed, Aug 28, 2019 at 10:46:34AM +1000, David Gibson wrote:
> > > > > On Tue, Aug 27, 2019 at 04:56:50PM +1000, Alexey Kardashevskiy wrote:
> > > > > > The following changes since commit d6bb8b27204eaa58f1da948b65454e3a598ab2a4:
> > > > > >
> > > > > > pseries: Update SLOF firmware image (2019-08-27 16:47:04 +1000)
> > > > > >
> > > > > > are available in the Git repository at:
> > > > > >
> > > > > > git@github.com:aik/qemu.git tags/qemu-slof-20190827
> > > > > >
> > > > > > for you to fetch changes up to da9960a5aaa25d27c9798c3d94c7b4c2d8af31ac:
> > > > > >
> > > > > > spapr: Render full FDT on ibm,client-architecture-support (2019-08-27 16:47:46 +1000)
> > > > > >
> > > > > > ----------------------------------------------------------------
> > > > > > Alexey Kardashevskiy (1):
> > > > > > spapr: Render full FDT on ibm,client-architecture-support
> > > > > >
> > > > > > hw/ppc/spapr.c | 90 +++++++---------------------------------------------------
> > > > > > 1 file changed, 10 insertions(+), 80 deletions(-)
> > > > > >
> > > > > >
> > > > > > *** Note: this is not for master, this is for pseries
> > > > > >
> > > > >
> > > > > Merged, thanks.
> > > >
> > > > Urgh. And the qemu change is now un-merged. Alas, as soon as we had
> > > > a CAS reboot for XIVE the guest didn't boot on the second attempt.
> > > > Haven't had a chance to investigate yet.
> > >
> > > QEMU command line, guest kernel version? I'd give it a try.
> >
> > RHEL8.1 in guest and host, booting via GRUB into a XIVE capable
> > kernel.
> >
> > I've now been able to investigate, dumping the dtb at H_UPDATE_DT
> > time.
>
> FWIW I sent a patch to do just that some times ago:
>
> https://patchwork.ozlabs.org/patch/1095705/
Yeah, I know. I didn't like adding yet another option as a permanent
fixture.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-08-29 1:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 6:56 [Qemu-devel] [GIT PULL for qemu-pseries] spapr: Render full FDT on ibm, client-architecture-support Alexey Kardashevskiy
2019-08-28 0:46 ` David Gibson
2019-08-28 2:12 ` David Gibson
2019-08-28 3:27 ` Alexey Kardashevskiy
2019-08-28 5:57 ` David Gibson
2019-08-28 9:50 ` [Qemu-devel] [Qemu-ppc] " Greg Kurz
2019-08-29 0:00 ` David Gibson [this message]
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=20190829000022.GD16342@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=aik@ozlabs.ru \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).