From: David Gibson <david@gibson.dropbear.id.au>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: linuxppc-dev@lists.ozlabs.org,
Suraj Jitindar Singh <sjitindarsingh@gmail.com>
Subject: Re: [PATCH kernel] prom_init: Fetch flatten device tree from the system firmware
Date: Thu, 2 May 2019 14:27:03 +1000 [thread overview]
Message-ID: <20190502042702.GH13618@umbus.fritz.box> (raw)
In-Reply-To: <20190501034221.18437-1-aik@ozlabs.ru>
[-- Attachment #1: Type: text/plain, Size: 4353 bytes --]
On Wed, May 01, 2019 at 01:42:21PM +1000, Alexey Kardashevskiy wrote:
> At the moment, on 256CPU + 256 PCI devices guest, it takes the guest
> about 8.5sec to fetch the entire device tree via the client interface
> as the DT is traversed twice - for strings blob and for struct blob.
> Also, "getprop" is quite slow too as SLOF stores properties in a linked
> list.
>
> However, since [1] SLOF builds flattened device tree (FDT) for another
> purpose. [2] adds a new "fdt-fetch" client interface for the OS to fetch
> the FDT.
>
> This tries the new method; if not supported, this falls back to
> the old method.
>
> There is a change in the FDT layout - the old method produced
> (reserved map, strings, structs), the new one receives only strings and
> structs from the firmware and adds the final reserved map to the end,
> so it is (fw reserved map, strings, structs, reserved map).
> This still produces the same unflattened device tree.
>
> This merges the reserved map from the firmware into the kernel's reserved
> map. At the moment SLOF generates an empty reserved map so this does not
> change the existing behaviour in regard of reservations.
>
> This supports only v17 onward as only that version provides dt_struct_size
> which works as "fdt-fetch" only produces v17 blobs.
>
> If "fdt-fetch" is not available, the old method of fetching the DT is used.
>
> [1] https://git.qemu.org/?p=SLOF.git;a=commitdiff;h=e6fc84652c9c00
> [2] https://git.qemu.org/?p=SLOF.git;a=commit;h=ecda95906930b80
>
> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Hrm. I've gotta say I'm not terribly convinced that it's worth adding
a new interface we'll need to maintain to save 8s on a somewhat
contrived testcase.
> ---
> arch/powerpc/kernel/prom_init.c | 43 +++++++++++++++++++++++++++++++++
> 1 file changed, 43 insertions(+)
>
> diff --git a/arch/powerpc/kernel/prom_init.c b/arch/powerpc/kernel/prom_init.c
> index f33ff4163a51..72e7a602b68e 100644
> --- a/arch/powerpc/kernel/prom_init.c
> +++ b/arch/powerpc/kernel/prom_init.c
> @@ -2457,6 +2457,48 @@ static void __init flatten_device_tree(void)
> prom_panic("Can't allocate initial device-tree chunk\n");
> mem_end = mem_start + room;
>
> + hdr = (void *) mem_start;
> + if (!call_prom_ret("fdt-fetch", 2, 1, NULL, mem_start,
> + room - sizeof(mem_reserve_map)) &&
> + hdr->version >= 17) {
> + u32 size;
> + struct mem_map_entry *fwrmap;
> +
> + /* Fixup the boot cpuid */
> + hdr->boot_cpuid_phys = cpu_to_be32(prom.cpu);
> +
> + /*
> + * Store the struct and strings addresses, mostly
> + * for consistency, only dt_header_start actually matters later.
> + */
> + dt_header_start = mem_start;
> + dt_string_start = mem_start + be32_to_cpu(hdr->off_dt_strings);
> + dt_string_end = dt_string_start +
> + be32_to_cpu(hdr->dt_strings_size);
> + dt_struct_start = mem_start + be32_to_cpu(hdr->off_dt_struct);
> + dt_struct_end = dt_struct_start +
> + be32_to_cpu(hdr->dt_struct_size);
> +
> + /*
> + * Calculate the reserved map location (which we put
> + * at the blob end) and update total size.
> + */
> + fwrmap = (void *)(mem_start + be32_to_cpu(hdr->off_mem_rsvmap));
> + hdr->off_mem_rsvmap = hdr->totalsize;
> + size = be32_to_cpu(hdr->totalsize);
> + hdr->totalsize = cpu_to_be32(size + sizeof(mem_reserve_map));
> +
> + /* Merge reserved map from firmware to ours */
> + for ( ; fwrmap->size; ++fwrmap)
> + reserve_mem(be64_to_cpu(fwrmap->base),
> + be64_to_cpu(fwrmap->size));
> +
> + rsvmap = (u64 *)(mem_start + size);
> +
> + prom_debug("Fetched DTB: %d bytes to @%lx\n", size, mem_start);
> + goto finalize_exit;
> + }
> +
> /* Get root of tree */
> root = call_prom("peer", 1, 1, (phandle)0);
> if (root == (phandle)0)
> @@ -2504,6 +2546,7 @@ static void __init flatten_device_tree(void)
> /* Version 16 is not backward compatible */
> hdr->last_comp_version = cpu_to_be32(0x10);
>
> +finalize_exit:
> /* Copy the reserve map in */
> memcpy(rsvmap, mem_reserve_map, sizeof(mem_reserve_map));
>
--
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-05-02 13:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 3:42 [PATCH kernel] prom_init: Fetch flatten device tree from the system firmware Alexey Kardashevskiy
2019-05-02 4:27 ` David Gibson [this message]
2019-05-03 0:10 ` Stewart Smith
2019-05-03 2:35 ` David Gibson
2019-05-06 2:21 ` Alexey Kardashevskiy
2019-05-03 15:35 ` Segher Boessenkool
2019-05-03 15:32 ` Segher Boessenkool
2019-05-30 7:09 ` Alexey Kardashevskiy
2019-05-30 19:37 ` Segher Boessenkool
2019-05-31 1:03 ` Benjamin Herrenschmidt
2019-06-02 23:23 ` Segher Boessenkool
2019-06-03 2:56 ` Alexey Kardashevskiy
2019-06-03 21:18 ` Benjamin Herrenschmidt
2019-06-03 23:49 ` Segher Boessenkool
2019-06-04 0:32 ` David Gibson
2019-06-03 23:42 ` Segher Boessenkool
2019-06-04 0:18 ` Benjamin Herrenschmidt
2019-06-04 5:00 ` 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=20190502042702.GH13618@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=aik@ozlabs.ru \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sjitindarsingh@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.