From: David Gibson <david@gibson.dropbear.id.au>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: lvivier@redhat.com, thuth@redhat.com, kvm@vger.kernel.org,
kvm-ppc@vger.kernel.org, rkrcmar@redhat.com
Subject: Re: [PATCH] powerpc: Fix up RTAS invocation for new qemu versions
Date: Mon, 7 Oct 2019 16:22:44 +1100 [thread overview]
Message-ID: <20191007052244.GA18815@umbus.fritz.box> (raw)
In-Reply-To: <22526d83-737f-c4aa-2fd5-84eb91b285d6@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]
On Sun, Oct 06, 2019 at 06:16:17PM +0200, Paolo Bonzini wrote:
> On 05/10/19 10:11, David Gibson wrote:
> > Fairly. First, we'd have to not use -bios to replace the normal SLOF
> > firmware - that could significantly slow down tests, since SLOF itself
> > takes a little while to start up.
>
> Oh, I forgot that PPC kvm-unit-tests use -bios. That makes
> everything moot.
Right. I did consider putting a closer-to-conventional RTAS blob in
kbm-unit-tests' special "firmware" (which currently consists of a
single jump instruction). It does help to build it BE which RTAS
expects. On the other hand, I wasn't about to implement a full OF
client interface, so it would still have the main part of the tests
relying on finding the blob at some well known location. And finding
a well known location that we can count on the tests proper not
clobbering is a bit of a pain as well.
--
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 --]
next prev parent reply other threads:[~2019-10-07 5:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 10:38 [PATCH] powerpc: Fix up RTAS invocation for new qemu versions David Gibson
2019-10-04 11:54 ` Paolo Bonzini
2019-10-05 8:11 ` David Gibson
2019-10-06 16:16 ` Paolo Bonzini
2019-10-07 5:22 ` David Gibson [this message]
2019-10-09 10:35 ` Thomas Huth
2019-10-09 11:12 ` Paolo Bonzini
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=20191007052244.GA18815@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.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