From: Ian Campbell <ian.campbell@citrix.com>
To: xen-devel@lists.xen.org
Cc: tim@xen.org, stefano.stabellini@citrix.com,
Ian Campbell <ian.campbell@citrix.com>
Subject: [PATCH 10/10] xen: strip /chosen/modules/module@<N>/* from dom0 device tree
Date: Fri, 18 Jan 2013 16:40:36 +0000 [thread overview]
Message-ID: <1358527236-2486-10-git-send-email-ian.campbell@citrix.com> (raw)
In-Reply-To: <1358526135.3279.103.camel@zakaz.uk.xensource.com>
These nodes are used by Xen to find the initial modules.
Only drop the "xen,multiboot-module" compatible nodes in case someone
else has a similar idea.
Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
---
v4 - /chosen/modules/modules@N not /chosen/module@N
v3 - use a helper to filter out DT elements which are not for dom0.
Better than an ad-hoc break in the middle of a loop.
---
xen/arch/arm/domain_build.c | 40 ++++++++++++++++++++++++++++++++++++++--
1 files changed, 38 insertions(+), 2 deletions(-)
diff --git a/xen/arch/arm/domain_build.c b/xen/arch/arm/domain_build.c
index 6abbb03..512d78c 100644
--- a/xen/arch/arm/domain_build.c
+++ b/xen/arch/arm/domain_build.c
@@ -172,6 +172,40 @@ static int write_properties(struct domain *d, struct kernel_info *kinfo,
return prop;
}
+/* Returns the next node in fdt (starting from offset) which should be
+ * passed through to dom0.
+ */
+static int fdt_next_dom0_node(const void *fdt, int node,
+ int *depth_out,
+ int parents[DEVICE_TREE_MAX_DEPTH])
+{
+ int depth = *depth_out;
+
+ while ( (node = fdt_next_node(fdt, node, &depth)) &&
+ node >= 0 && depth >= 0 )
+ {
+ if ( depth >= DEVICE_TREE_MAX_DEPTH )
+ break;
+
+ parents[depth] = node;
+
+ /* Skip /chosen/modules/module@<N>/ and all subnodes */
+ if ( depth >= 3 &&
+ device_tree_node_matches(fdt, parents[1], "chosen") &&
+ device_tree_node_matches(fdt, parents[2], "modules") &&
+ device_tree_node_matches(fdt, parents[3], "module") &&
+ fdt_node_check_compatible(fdt, parents[3],
+ "xen,multiboot-module" ) == 0 )
+ continue;
+
+ /* We've arrived at a node which dom0 is interested in. */
+ break;
+ }
+
+ *depth_out = depth;
+ return node;
+}
+
static int write_nodes(struct domain *d, struct kernel_info *kinfo,
const void *fdt)
{
@@ -179,11 +213,12 @@ static int write_nodes(struct domain *d, struct kernel_info *kinfo,
int depth = 0, last_depth = -1;
u32 address_cells[DEVICE_TREE_MAX_DEPTH];
u32 size_cells[DEVICE_TREE_MAX_DEPTH];
+ int parents[DEVICE_TREE_MAX_DEPTH];
int ret;
for ( node = 0, depth = 0;
node >= 0 && depth >= 0;
- node = fdt_next_node(fdt, node, &depth) )
+ node = fdt_next_dom0_node(fdt, node, &depth, parents) )
{
const char *name;
@@ -191,7 +226,8 @@ static int write_nodes(struct domain *d, struct kernel_info *kinfo,
if ( depth >= DEVICE_TREE_MAX_DEPTH )
{
- printk("warning: node `%s' is nested too deep\n", name);
+ printk("warning: node `%s' is nested too deep (%d)\n",
+ name, depth);
continue;
}
--
1.7.9.1
prev parent reply other threads:[~2013-01-18 16:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 16:22 [PATCH 00/10 V5] arm: support for initial modules (e.g. dom0) and DTB supplied in RAM Ian Campbell
2013-01-18 16:40 ` [PATCH 01/10] xen: arm: introduce concept of modules which can be in RAM at start of day Ian Campbell
2013-01-21 11:35 ` Stefano Stabellini
2013-01-21 12:41 ` Ian Campbell
2013-01-18 16:40 ` [PATCH 02/10] arm: avoid placing Xen over any modules Ian Campbell
2013-01-18 16:40 ` [PATCH 03/10] arm: avoid allocating the heaps over modules or xen itself Ian Campbell
2013-01-18 16:40 ` [PATCH 04/10] device-tree: get_val cannot cope with cells > 2, add early_panic Ian Campbell
2013-01-18 16:40 ` [PATCH 05/10] arm: load dom0 kernel from first boot module Ian Campbell
2013-01-18 16:40 ` [PATCH 06/10] arm: discard boot modules after building domain 0 Ian Campbell
2013-01-18 16:40 ` [PATCH 07/10] arm: use module provided command line for domain 0 command line Ian Campbell
2013-01-18 16:40 ` [PATCH 08/10] xen/arm: flush dcache after memcpy'ing the kernel image Ian Campbell
2013-01-18 16:40 ` [PATCH 09/10] xen: arm: parse modules from DT during early boot Ian Campbell
2013-01-18 16:40 ` Ian Campbell [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=1358527236-2486-10-git-send-email-ian.campbell@citrix.com \
--to=ian.campbell@citrix.com \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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).