From: Thomas Huth <thuth@redhat.com>
To: Eric Auger <eric.auger@linaro.org>,
eric.auger@st.com, qemu-devel@nongnu.org, qemu-arm@nongnu.org,
alex.williamson@redhat.com, peter.maydell@linaro.org
Cc: thomas.lendacky@amd.com, b.reynal@virtualopensystems.com,
patches@linaro.org, suravee.suthikulpanit@amd.com,
pbonzini@redhat.com, christoffer.dall@linaro.org,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [RESEND RFC 2/6] device_tree: introduce load_device_tree_from_sysfs
Date: Thu, 26 Nov 2015 11:57:20 +0100 [thread overview]
Message-ID: <5656E590.3040001@redhat.com> (raw)
In-Reply-To: <1447946528-1533-3-git-send-email-eric.auger@linaro.org>
On 19/11/15 16:22, Eric Auger wrote:
> This function returns the host device tree blob from sysfs
> (/sys/firmware/devicetree/base).
>
> This has a runtime dependency on the dtc binary. This functionality
> is useful for platform device passthrough where the host device tree
> needs to be parsed to feed information into the guest device tree.
>
> Signed-off-by: Eric Auger <eric.auger@linaro.org>
> ---
> device_tree.c | 40 ++++++++++++++++++++++++++++++++++++++++
> include/sysemu/device_tree.h | 1 +
> 2 files changed, 41 insertions(+)
>
> diff --git a/device_tree.c b/device_tree.c
> index a9f5f8e..58a5329 100644
> --- a/device_tree.c
> +++ b/device_tree.c
> @@ -117,6 +117,46 @@ fail:
> return NULL;
> }
>
> +/**
> + * load_device_tree_from_sysfs
> + *
> + * extract the dt blob from host sysfs
> + * this has a runtime dependency on the dtc binary
> + */
> +void *load_device_tree_from_sysfs(void)
> +{
> + char cmd[] = "dtc -I fs -O dtb /sys/firmware/devicetree/base";
> + FILE *pipe;
> + void *fdt;
> + int ret, actual_dt_size;
> +
> + pipe = popen(cmd, "r");
> + if (!pipe) {
> + error_report("%s: Error when executing dtc", __func__);
> + return NULL;
> + }
The Device Tree Compiler binary is normally only installed on
developer's machines, so I somewhat doubt that it is a good idea to rely
on the availability of that binary in QEMU? Maybe you should rather
extend libfdt to support such a feature?
Thomas
next prev parent reply other threads:[~2015-11-26 10:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 15:22 [Qemu-devel] [RESEND RFC 0/6] AMD XGBE KVM platform passthrough Eric Auger
2015-11-19 15:22 ` [Qemu-devel] [RESEND RFC 1/6] hw/vfio/platform: amd-xgbe device Eric Auger
2015-11-25 14:35 ` Alex Bennée
2015-11-19 15:22 ` [Qemu-devel] [RESEND RFC 2/6] device_tree: introduce load_device_tree_from_sysfs Eric Auger
2015-11-25 15:38 ` Alex Bennée
2015-11-26 10:57 ` Thomas Huth [this message]
2015-12-03 15:19 ` Eric Auger
2015-11-19 15:22 ` [Qemu-devel] [RESEND RFC 3/6] device_tree: introduce qemu_fdt_node_path Eric Auger
2015-11-26 12:06 ` Alex Bennée
2015-12-03 15:44 ` Eric Auger
2015-11-19 15:22 ` [Qemu-devel] [RESEND RFC 4/6] device_tree: introduce qemu_fdt_getprop_optional Eric Auger
2015-11-26 13:13 ` Alex Bennée
2015-11-27 19:38 ` Peter Crosthwaite
2015-12-03 15:48 ` Eric Auger
2015-11-19 15:22 ` [Qemu-devel] [RESEND RFC 5/6] hw/arm/sysbus-fdt: helpers for clock node generation Eric Auger
2015-11-26 16:06 ` Alex Bennée
2015-12-17 9:26 ` Eric Auger
2015-12-17 13:28 ` Alex Bennée
2015-12-17 13:44 ` Peter Maydell
2015-12-17 15:13 ` Alex Bennée
2015-12-17 15:25 ` Eric Auger
2015-12-17 15:56 ` Alex Bennée
2015-11-19 15:22 ` [Qemu-devel] [RESEND RFC 6/6] hw/arm/sysbus-fdt: enable amd-xgbe dynamic instantiation Eric Auger
2015-11-26 17:14 ` Alex Bennée
2015-12-03 16:17 ` Eric Auger
2015-11-19 23:44 ` [Qemu-devel] [RESEND RFC 0/6] AMD XGBE KVM platform passthrough Alex Williamson
2015-11-20 15:10 ` Eric Auger
2015-11-25 10:29 ` Christoffer Dall
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=5656E590.3040001@redhat.com \
--to=thuth@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=b.reynal@virtualopensystems.com \
--cc=christoffer.dall@linaro.org \
--cc=david@gibson.dropbear.id.au \
--cc=eric.auger@linaro.org \
--cc=eric.auger@st.com \
--cc=patches@linaro.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=thomas.lendacky@amd.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).