From: Eric Auger <eric.auger@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Baptiste Reynal" <b.reynal@virtualopensystems.com>,
"Thomas Huth" <thuth@redhat.com>,
eric.auger@st.com, "Patch Tracking" <patches@linaro.org>,
"Peter Crosthwaite" <crosthwaitepeter@gmail.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Alex Williamson" <alex.williamson@redhat.com>,
"Suravee Suthikulpanit" <suravee.suthikulpanit@amd.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
thomas.lendacky@amd.com, "Alex Bennée" <alex.bennee@linaro.org>,
"Christoffer Dall" <christoffer.dall@linaro.org>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH 5/6] hw/arm/sysbus-fdt: helpers for clock node generation
Date: Tue, 5 Jan 2016 18:04:57 +0100 [thread overview]
Message-ID: <568BF7B9.8080708@linaro.org> (raw)
In-Reply-To: <CAFEAcA-PN0rBOBED5=DqVpZkcYFNHuAUM28Db01XR9ckihGvoA@mail.gmail.com>
On 12/18/2015 03:54 PM, Peter Maydell wrote:
> On 17 December 2015 at 12:29, Eric Auger <eric.auger@linaro.org> wrote:
>> Some passthrough'ed devices depend on clock nodes. Those need to be
>> generated in the guest device tree. This patch introduces some helpers
>> to build a clock node from information retrieved in the host device tree.
>>
>> - inherit_properties copies properties from a host device tree node to
>> a guest device tree node
>> - fdt_build_clock_node builds a guest clock node and checks the host
>> fellow clock is a fixed one.
>>
>> fdt_build_clock_node will become static as soon as it gets used. A
>> dummy pre-declaration is needed for compilation of this patch.
>>
>> Signed-off-by: Eric Auger <eric.auger@linaro.org>
>>
>> ---
>>
>> RFC -> v1:
>> - use the new proto of qemu_fdt_getprop
>> - remove newline in error_report
>> - fix some style issues
>> ---
>> hw/arm/sysbus-fdt.c | 111 ++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 111 insertions(+)
>>
>> diff --git a/hw/arm/sysbus-fdt.c b/hw/arm/sysbus-fdt.c
>> index 9d28797..c2d813b 100644
>> --- a/hw/arm/sysbus-fdt.c
>> +++ b/hw/arm/sysbus-fdt.c
>> @@ -21,6 +21,7 @@
>> *
>> */
>>
>> +#include <libfdt.h>
>> #include "hw/arm/sysbus-fdt.h"
>> #include "qemu/error-report.h"
>> #include "sysemu/device_tree.h"
>> @@ -56,6 +57,116 @@ typedef struct NodeCreationPair {
>> int (*add_fdt_node_fn)(SysBusDevice *sbdev, void *opaque);
>> } NodeCreationPair;
>>
>> +/* helpers */
>> +
>> +struct HostProperty {
>> + const char *name;
>> + bool optional;
>> +};
>> +
>> +typedef struct HostProperty HostProperty;
>
> You can combine the typedef and the struct declaration if you like.
ok
>
>> +
>> +/**
>> + * inherit_properties
>> + *
>> + * copies properties listed in an array from host device tree to
>> + * guest device tree. If a non optional property is not found, the
>> + * function self-asserts. An optional property is ignored if not found
>> + * in the host device tree.
>> + * @props: array of HostProperty to copy
>> + * @nb_props: number of properties in the array
>> + * @host_dt: host device tree blob
>> + * @guest_dt: guest device tree blob
>> + * @node_path: host dt node path where the property is supposed to be
>> + found
>> + * @nodename: guest node name the properties should be added to
>> + */
>> +static void inherit_properties(HostProperty *props, int nb_props,
>> + void *host_fdt, void *guest_fdt,
>> + char *node_path, char *nodename)
>> +{
>> + int i, prop_len;
>> + const void *r;
>> +
>> + for (i = 0; i < nb_props; i++) {
>> + r = qemu_fdt_getprop(host_fdt, node_path,
>> + props[i].name,
>> + &prop_len,
>> + props[i].optional ? NULL : &error_fatal);
>
> We'll get an error here if the host device tree doesn't match
> up correctly, right? Is the error message going to be sufficiently
> informative to the end user about what's gone wrong? (What does
> it end up looking like?)
hum you're right, in case of a mandated property there is auto-assert
with a good error message.
In case of an optional property, there is currently no message output to
the end-user and the host property is ignored/not propagated to the
guest, with potential functional consequences. I intend to use an error
object instead and print the error message in case the error is !=
FDT_ERR_NOTFOUND.
>
>> + if (r) {
>> + qemu_fdt_setprop(guest_fdt, nodename,
>> + props[i].name, r, prop_len);
>> + }
>> + }
>> +}
>> +
>> +/* clock properties whose values are copied/pasted from host */
>> +static HostProperty clock_inherited_properties[] = {
>> + {"compatible", 0},
>> + {"#clock-cells", 0},
>> + {"clock-frequency", 1},
>> + {"clock-output-names", 1},
>> +};
>> +
>> +/**
>> + * fdt_build_clock_node
>> + *
>> + * Build a guest clock node, used as a dependency from a passthrough'ed
>> + * device. Most information are retrieved from the host clock node.
>> + * Also check the host clock is a fixed one.
>> + *
>> + * @host_fdt: host device tree blob from which info are retrieved
>> + * @guest_fdt: guest device tree blob where the clock node is added
>> + * @host_phandle: phandle of the clock in host device tree
>> + * @guest_phandle: phandle to assign to the guest node
>> + */
>> +int fdt_build_clock_node(void *host_fdt, void *guest_fdt,
>> + uint32_t host_phandle,
>> + uint32_t guest_phandle);
>> +int fdt_build_clock_node(void *host_fdt, void *guest_fdt,
>> + uint32_t host_phandle,
>> + uint32_t guest_phandle)
>> +{
>> + char node_path[256];
>
> Please don't use hardcoded fixed buffer lengths (see previous patch
> review comments).
OK
>
>> + char *nodename;
>> + const void *r;
>> + int ret, prop_len;
>> +
>> + ret = fdt_node_offset_by_phandle(host_fdt, host_phandle);
>> + if (ret <= 0) {
>> + error_report("not able to locate clock handle %d in host device tree",
>> + host_phandle);
>> + goto out;
>> + }
>
> If we're going to return to the caller in the error case rather than just
> exiting here, I think we should return the error to the caller via an
> Error** rather than calling error_report() directly ourselves.
agreed
Thanks!
Eric
>
>> + ret = fdt_get_path(host_fdt, ret, node_path, 256);
>> + if (ret < 0) {
>> + error_report("not able to retrieve node path for clock handle %d",
>> + host_phandle);
>> + goto out;
>> + }
>> +
>> + r = qemu_fdt_getprop(host_fdt, node_path, "compatible", &prop_len,
>> + &error_fatal);
>> + if (strcmp(r, "fixed-clock")) {
>> + error_report("clock handle %d is not a fixed clock", host_phandle);
>> + ret = -1;
>> + goto out;
>> + }
>> +
>> + nodename = strrchr(node_path, '/');
>> + qemu_fdt_add_subnode(guest_fdt, nodename);
>> +
>> + inherit_properties(clock_inherited_properties,
>> + ARRAY_SIZE(clock_inherited_properties),
>> + host_fdt, guest_fdt,
>> + node_path, nodename);
>> +
>> + qemu_fdt_setprop_cell(guest_fdt, nodename, "phandle", guest_phandle);
>> +
>> +out:
>> + return ret;
>> +}
>> +
>> /* Device Specific Code */
>
> thanks
> -- PMM
>
next prev parent reply other threads:[~2016-01-05 17:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 12:29 [Qemu-devel] [PATCH 0/6] AMD XGBE KVM platform passthrough Eric Auger
2015-12-17 12:29 ` [Qemu-devel] [PATCH 1/6] hw/vfio/platform: amd-xgbe device Eric Auger
2015-12-18 13:53 ` Peter Maydell
2015-12-17 12:29 ` [Qemu-devel] [PATCH 2/6] device_tree: introduce load_device_tree_from_sysfs Eric Auger
2015-12-18 14:10 ` Peter Maydell
2016-01-04 17:37 ` Eric Auger
2016-01-04 21:33 ` Peter Maydell
2015-12-17 12:29 ` [Qemu-devel] [PATCH 3/6] device_tree: introduce qemu_fdt_node_path Eric Auger
2015-12-18 14:23 ` Peter Maydell
2016-01-05 16:20 ` Eric Auger
2016-01-05 17:55 ` Peter Maydell
2016-01-06 8:43 ` Eric Auger
2015-12-17 12:29 ` [Qemu-devel] [PATCH 4/6] device_tree: qemu_fdt_getprop converted to use the error API Eric Auger
2015-12-18 14:36 ` Peter Maydell
2016-01-05 16:20 ` Eric Auger
2016-01-05 17:54 ` Peter Maydell
2015-12-17 12:29 ` [Qemu-devel] [PATCH 5/6] hw/arm/sysbus-fdt: helpers for clock node generation Eric Auger
2015-12-18 14:54 ` Peter Maydell
2016-01-05 17:04 ` Eric Auger [this message]
2015-12-17 12:29 ` [Qemu-devel] [PATCH 6/6] hw/arm/sysbus-fdt: enable amd-xgbe dynamic instantiation Eric Auger
2015-12-18 15:05 ` Peter Maydell
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=568BF7B9.8080708@linaro.org \
--to=eric.auger@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=alex.williamson@redhat.com \
--cc=b.reynal@virtualopensystems.com \
--cc=christoffer.dall@linaro.org \
--cc=crosthwaitepeter@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=eric.auger@st.com \
--cc=patches@linaro.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=thomas.lendacky@amd.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;
as well as URLs for NNTP newsgroup(s).