From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH qemu] spapr: Render full FDT on ibm, client-architecture-support
Date: Tue, 27 Aug 2019 11:41:13 +1000 [thread overview]
Message-ID: <4692fae3-bcae-4221-6c1b-064a02111d1f@ozlabs.ru> (raw)
In-Reply-To: <20190826074431.GA28081@umbus.fritz.box>
On 26/08/2019 17:44, David Gibson wrote:
> On Mon, Aug 26, 2019 at 02:31:26PM +1000, Alexey Kardashevskiy wrote:
>> The ibm,client-architecture-support call is a way for the guest to
>> negotiate capabilities with a hypervisor. It is implemented as:
>> - the guest calls SLOF via client interface;
>> - SLOF calls QEMU (H_CAS hypercall) with an options vector from the guest;
>> - QEMU returns a device tree diff (which uses FDT format with
>> an additional header before it);
>> - SLOF walks through the partial diff tree and updates its internal tree
>> with the values from the diff.
>>
>> This changes QEMU to simply re-render the entire tree and send it as
>> an update. SLOF can handle this already mostly, [1] is needed before this
>> can be applied.
>>
>> The benefit is reduced code size as there is no need for another set of
>> DT rendering helpers such as spapr_fixup_cpu_dt().
>>
>> The downside is that the updates are bigger now (as they include all
>> nodes and properties) but the difference on a '-smp 256,threads=1' system
>> before/after is 2.35s vs. 2.5s.
>>
>> While at this, add a missing g_free(fdt) if the resulting tree is bigger
>> than the space allocated by SLOF. Also, store the resulting tree in
>> the spapr machine to have the latest valid FDT copy possible (this should
>> not matter much as H_UPDATE_DT happens right after that but nevertheless).
>>
>> [1] https://patchwork.ozlabs.org/patch/1152915/
>>
>> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
>
> Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
>
> Can you wrap that up with the SLOF update in a pull request for me?
Yup, I'll just wait a little bit more for replies about the RTAS log
extension patch. Cheers,
--
Alexey
prev parent reply other threads:[~2019-08-27 1:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 4:31 [Qemu-devel] [PATCH qemu] spapr: Render full FDT on ibm, client-architecture-support Alexey Kardashevskiy
2019-08-26 7:44 ` David Gibson
2019-08-27 1:41 ` Alexey Kardashevskiy [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=4692fae3-bcae-4221-6c1b-064a02111d1f@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--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).