All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <ian.campbell@citrix.com>, xen-devel@lists.xen.org
Cc: tim@xen.org, stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH v2 8/8] xen: arm: allocate more than one bank for 1:1 domain 0 if needed
Date: Wed, 11 Jun 2014 23:47:39 +0100	[thread overview]
Message-ID: <5398DC8B.5020706@linaro.org> (raw)
In-Reply-To: <1402504804-29173-8-git-send-email-ian.campbell@citrix.com>

Hi Ian,

On 11/06/14 17:40, Ian Campbell wrote:
> +        bank->start = start;
> +        bank->size = size;
> +        kinfo->mem.nr_banks++;
> +        return true;
> +    }
> +
> +    panic("Failed add pages to DOM0 memory bank");

This can happen when there is no more bank, right? How likely will Xen 
fill the 8 banks?

Shall we just continue with only the current number of bank?

> +}
> +
> +/*
> + * This is all pretty horrible.
> + *
> + * Requirements:
> + *
> + * 1. The dom0 kernel should be loaded within the first 128MB of RAM. This
> + *    is necessary at least for Linux zImage kernels, which are all we
> + *    support today.
> + * 2. We want to put the dom0 kernel, ramdisk and DTB in the same
> + *    bank. Partly this is just easier for us to deal with, but also
> + *    the ramdisk and DTB must be placed within a certain proximity of
> + *    the kernel within RAM.
> + * 3. For 32-bit dom0 we want to place as much of the RAM as we
> + *    reasonably can below 4GB, so that it can be used by non-LPAE
> + *    enabled kernels.
> + * 4. For 32-bit dom0 the kernel must be located below 4GB.
> + * 5. We want to have a few largers banks rather than many smaller ones.
> + *
> + * For the first two requirements we need to make sure that the lowest
> + * bank is sufficiently large.
> + *
> + * For convenience we also sort the banks by physical address.

IIRC, some kernel version (< 3.15) is assuming that the memory bank are 
ordered.

Regards,

-- 
Julien Grall

  reply	other threads:[~2014-06-11 22:47 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11 16:37 [PATCH v2 0/8] xen: arm: Use super pages in p2m Ian Campbell
2014-06-11 16:39 ` [PATCH v2 1/8] xen: arm: dump vcpu gic info in arch_dump_vcpu_info Ian Campbell
2014-06-11 16:39 ` [PATCH v2 2/8] tools/libxc: pull min/max_t into xc_private.h Ian Campbell
2014-06-11 21:14   ` Julien Grall
2014-06-11 16:39 ` [PATCH v2 3/8] tools: arm: allocate large pages to guests Ian Campbell
2014-06-11 21:26   ` Julien Grall
2014-06-12  7:19     ` Ian Campbell
2014-06-12  8:47       ` Julien Grall
2014-06-11 16:40 ` [PATCH v2 4/8] xen: arm: only put_page for p2m operations which require it Ian Campbell
2014-06-11 21:31   ` Julien Grall
2014-06-12  7:27     ` Ian Campbell
2014-06-11 16:40 ` [PATCH v2 5/8] xen: arm: handle superpage mappings in p2m_lookup Ian Campbell
2014-06-11 16:40 ` [PATCH v2 6/8] xen: arm: add some helpers for assessing p2m pte Ian Campbell
2014-06-11 21:39   ` Julien Grall
2014-06-12  7:27     ` Ian Campbell
2014-06-11 16:40 ` [PATCH v2 7/8] xen: arm: use superpages in p2m when pages are suitably aligned Ian Campbell
2014-06-11 22:19   ` Julien Grall
2014-06-12  7:30     ` Ian Campbell
2014-06-12  9:00       ` Julien Grall
2014-06-13 14:08         ` Ian Campbell
2014-06-13 17:45           ` Julien Grall
2014-06-16  8:26             ` Jan Beulich
2014-06-16  9:53             ` Ian Campbell
2014-06-12 13:57   ` Stefano Stabellini
2014-06-13 14:15     ` Ian Campbell
2014-06-11 16:40 ` [PATCH v2 8/8] xen: arm: allocate more than one bank for 1:1 domain 0 if needed Ian Campbell
2014-06-11 22:47   ` Julien Grall [this message]
2014-06-12  7:31     ` Ian Campbell
2014-06-17 17:58   ` Julien Grall
2014-06-18  8:27     ` Ian Campbell
2014-06-18  9:10       ` Julien Grall
2014-06-18  9:36         ` Ian Campbell
2014-06-12  7:20 ` [PATCH v2 0/8] xen: arm: Use super pages in p2m 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=5398DC8B.5020706@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=ian.campbell@citrix.com \
    --cc=stefano.stabellini@eu.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 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.