From: Ian Campbell <ian.campbell@citrix.com>
To: xen-devel@lists.xen.org
Cc: Ian Campbell <ian.campbell@citrix.com>
Subject: [PATCH 05/12] arm: avoid placing Xen over any modules.
Date: Tue, 13 Nov 2012 16:23:17 +0000 [thread overview]
Message-ID: <1352823804-28482-5-git-send-email-ian.campbell@citrix.com> (raw)
In-Reply-To: <1352823779.7491.94.camel@zakaz.uk.xensource.com>
This will still fail if the modules are such that Xen is pushed out of
the top 32M of RAM since it will then overlap with the domheap (or
possibly xenheap). This will be dealt with later.
Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
Acked-by: Tim Deegan <tim@xen.org>
---
v2: Xen is module 0, modules start at 1.
---
xen/arch/arm/setup.c | 68 ++++++++++++++++++++++++++++++++++++++++++++-----
1 files changed, 61 insertions(+), 7 deletions(-)
diff --git a/xen/arch/arm/setup.c b/xen/arch/arm/setup.c
index b0b30d6..587b1e7 100644
--- a/xen/arch/arm/setup.c
+++ b/xen/arch/arm/setup.c
@@ -68,17 +68,55 @@ static void __init processor_id(void)
READ_CP32(ID_ISAR3), READ_CP32(ID_ISAR4), READ_CP32(ID_ISAR5));
}
+/*
+ * Returns the end address of the highest region in the range s..e
+ * with required size and alignment that does not conflict with the
+ * modules from first_mod to nr_modules.
+ *
+ * For non-recursive callers first_mod should normally be 1.
+ */
+static paddr_t __init consider_modules(paddr_t s, paddr_t e,
+ uint32_t size, paddr_t align,
+ int first_mod)
+{
+ const struct dt_module_info *mi = &early_info.modules;
+ int i;
+
+ s = (s+align-1) & ~(align-1);
+ e = e & ~(align-1);
+
+ if ( s > e || e - s < size )
+ return 0;
+
+ for ( i = first_mod; i <= mi->nr_mods; i++ )
+ {
+ paddr_t mod_s = mi->module[i].start;
+ paddr_t mod_e = mod_s + mi->module[i].size;
+
+ if ( s < mod_e && mod_s < e )
+ {
+ mod_e = consider_modules(mod_e, e, size, align, i+1);
+ if ( mod_e )
+ return mod_e;
+
+ return consider_modules(s, mod_s, size, align, i+1);
+ }
+ }
+
+ return e;
+}
+
/**
* get_xen_paddr - get physical address to relocate Xen to
*
- * Xen is relocated to the top of RAM and aligned to a XEN_PADDR_ALIGN
- * boundary.
+ * Xen is relocated to as near to the top of RAM as possible and
+ * aligned to a XEN_PADDR_ALIGN boundary.
*/
static paddr_t __init get_xen_paddr(void)
{
struct dt_mem_info *mi = &early_info.mem;
paddr_t min_size;
- paddr_t paddr = 0, t;
+ paddr_t paddr = 0;
int i;
min_size = (_end - _start + (XEN_PADDR_ALIGN-1)) & ~(XEN_PADDR_ALIGN-1);
@@ -86,17 +124,33 @@ static paddr_t __init get_xen_paddr(void)
/* Find the highest bank with enough space. */
for ( i = 0; i < mi->nr_banks; i++ )
{
- if ( mi->bank[i].size >= min_size )
+ const struct membank *bank = &mi->bank[i];
+ paddr_t s, e;
+
+ if ( bank->size >= min_size )
{
- t = mi->bank[i].start + mi->bank[i].size - min_size;
- if ( t > paddr )
- paddr = t;
+ e = consider_modules(bank->start, bank->start + bank->size,
+ min_size, XEN_PADDR_ALIGN, 1);
+ if ( !e )
+ continue;
+
+ s = e - min_size;
+
+ if ( s > paddr )
+ paddr = s;
}
}
if ( !paddr )
early_panic("Not enough memory to relocate Xen\n");
+ early_printk("Placing Xen at 0x%"PRIpaddr"-0x%"PRIpaddr"\n",
+ paddr, paddr + min_size);
+
+ /* Xen is module 0 */
+ early_info.modules.module[0].start = paddr;
+ early_info.modules.module[0].size = min_size;
+
return paddr;
}
--
1.7.9.1
next prev parent reply other threads:[~2012-11-13 16:23 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 16:22 [PATCH V2 00/12] arm: support for initial modules (e.g. dom0) and DTB supplied in RAM Ian Campbell
2012-11-13 16:23 ` [PATCH 01/12] arm: Enable build without CONFIG_DTB_FILE Ian Campbell
2012-11-13 16:23 ` [PATCH 02/12] arm: create a raw binary target Ian Campbell
2012-11-13 16:23 ` [PATCH 03/12] arm: handle xenheap which isn't at the start of RAM Ian Campbell
2012-11-13 16:23 ` [PATCH 04/12] arm: parse modules from DT during early boot Ian Campbell
2012-11-29 17:05 ` Tim Deegan
2012-11-29 17:13 ` Ian Campbell
2012-11-30 15:14 ` Stefano Stabellini
2012-11-30 15:11 ` Stefano Stabellini
2012-12-03 16:19 ` Ian Campbell
2012-12-04 12:42 ` Stefano Stabellini
2012-12-04 13:44 ` Ian Campbell
2012-11-13 16:23 ` Ian Campbell [this message]
2012-11-13 16:23 ` [PATCH 06/12] arm: avoid allocating the heaps over modules or xen itself Ian Campbell
2012-11-29 17:06 ` Tim Deegan
2012-11-29 17:19 ` Ian Campbell
2012-11-29 17:45 ` Tim Deegan
2012-11-13 16:23 ` [PATCH 07/12] arm: const-correctness in virt_to_maddr Ian Campbell
2012-11-13 16:23 ` [PATCH 08/12] device-tree: get_val cannot cope with cells > 2, add a BUG Ian Campbell
2012-11-29 17:09 ` Tim Deegan
2012-11-29 17:14 ` Ian Campbell
2012-11-13 16:23 ` [PATCH 09/12] arm: load dom0 kernel from first boot module Ian Campbell
2012-11-29 17:15 ` Tim Deegan
2012-11-29 17:24 ` Ian Campbell
2012-11-29 17:55 ` Tim Deegan
2012-11-13 16:23 ` [PATCH 10/12] arm: discard boot modules after building domain 0 Ian Campbell
2012-11-13 16:23 ` [PATCH 11/12] arm: use /chosen/module@1/bootargs for domain 0 command line Ian Campbell
2012-11-13 16:23 ` [PATCH 12/12] xen: strip /chosen/module@<N>/* from dom0 device tree Ian Campbell
2012-11-13 16:38 ` [PATCH V2 00/12] arm: support for initial modules (e.g. dom0) and DTB supplied in RAM Ian Campbell
2012-11-29 17:59 ` Tim Deegan
2012-11-29 18:05 ` Ian Campbell
2012-11-30 12:20 ` Ian Campbell
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=1352823804-28482-5-git-send-email-ian.campbell@citrix.com \
--to=ian.campbell@citrix.com \
--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).