All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: stefano.stabellini@eu.citrix.com, tim@xen.org,
	Andre Przywara <andre.przywara@linaro.org>,
	xen-devel@lists.xen.org, Chen Baozi <baozich@gmail.com>,
	Anup Patel <apatel@apm.com>,
	Pranavkumar Sawargaonkar <psawargaonkar@apm.com>
Subject: Re: [PATCH] xen: arm: remove hardcoded gnttab location from dom0
Date: Tue, 03 Dec 2013 15:20:37 +0000	[thread overview]
Message-ID: <529DF6C5.2050703@linaro.org> (raw)
In-Reply-To: <1386083062-30104-1-git-send-email-ian.campbell@citrix.com>

On 12/03/2013 03:04 PM, Ian Campbell wrote:
> The DT provided to guests (including dom0) includes a Xen node which, among
> other things, describes an MMIO region which can be safely used for grant
> table mappings (i.e. it is a hole in the physical address space). For domU we
> provide a hardcoded values based on our hardcoded guest virtual machine
> layout. However for dom0 we need to fit in with the underlying platform.
> Leaving this hardcoded was an oversight which on some platforms could result
> in the grant table overlaying RAM or MMIO regions which are in use by domain
> 0.
> 
> For the 4.4 release do as we did with the dom0 evtchn PPI and provide a hook
> for the platform code to supply a suitable hardcoded address for the platform
> (derived from reading the data sheet). Platforms which do not provide the hook
> get the existing address as a default.
> 
> After 4.4 we should switch to selecting a region of host RAM which is not RAM
> in the guest address map. This should be more flexible and safer but the patch
> was looking too complex for 4.4.
> 
> Platform        Gnttab Address
> ========        ==============
> exynos5.c       0xb0000000, confirmed with Julien.
> sunxi.c         0x01d00000, confirmed in data sheet.
> midway.c        0xff800000, confirmed with Andre, boot tested.
> vexpress.c      0xb0000000, existing hardcoded value was selected for vexpress.
> omap5.c         0xb0000000, no datasheet, looks safe in DTB.
> xgene-storm.c   0x1f800000, reserved according to datasheet, boot tested.
> 
> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> Cc: Julien.Grall@linaro.org
> Cc: Stefano.Stabellini@eu.citrix.com
> Cc: Andre Przywara <andre.przywara@linaro.org>
> Cc: Chen Baozi <baozich@gmail.com>
> Cc: Pranavkumar Sawargaonkar <psawargaonkar@apm.com>
> Cc: Anup Patel <apatel@apm.com>
> ---
>  xen/arch/arm/domain_build.c          |    7 +++++--
>  xen/arch/arm/platform.c              |   14 ++++++++++++++
>  xen/arch/arm/platforms/midway.c      |    3 +++
>  xen/arch/arm/platforms/sunxi.c       |    3 +++
>  xen/arch/arm/platforms/xgene-storm.c |    3 +++
>  xen/include/asm-arm/platform.h       |    7 +++++++
>  6 files changed, 35 insertions(+), 2 deletions(-)
> 
> diff --git a/xen/arch/arm/domain_build.c b/xen/arch/arm/domain_build.c
> index be39686..332e937 100644
>  
>  /*
> diff --git a/xen/include/asm-arm/platform.h b/xen/include/asm-arm/platform.h
> index 5900ee4..bda4e41 100644
> --- a/xen/include/asm-arm/platform.h
> +++ b/xen/include/asm-arm/platform.h
> @@ -41,6 +41,12 @@ struct platform_desc {
>       * The IRQ (PPI) to use to inject event channels to dom0.
>       */
>      unsigned int dom0_evtchn_ppi;
> +    /*
> +     * The location of a region of physical address space which dom0
> +     * can use for grant table mappings. If size is zero defaults to
> +     * 0xb0000000-0xb0020000.
> +     */
> +    paddr_t dom0_gnttab_start, dom0_gnttab_size;

The size looks the same everywhere, can we just hardcode the base
address per platform?

-- 
Julien Grall

  reply	other threads:[~2013-12-03 15:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-03 15:04 [PATCH] xen: arm: remove hardcoded gnttab location from dom0 Ian Campbell
2013-12-03 15:20 ` Julien Grall [this message]
2013-12-03 15:22   ` Ian Campbell
2013-12-03 15:52     ` Julien Grall
2013-12-03 15:32 ` Andre Przywara
2013-12-03 18:18 ` Chen Baozi
2013-12-04  9:58   ` Ian Campbell
2013-12-04 14:49     ` Chen Baozi
2013-12-04  7:27 ` Pranavkumar Sawargaonkar

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=529DF6C5.2050703@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=andre.przywara@linaro.org \
    --cc=apatel@apm.com \
    --cc=baozich@gmail.com \
    --cc=ian.campbell@citrix.com \
    --cc=psawargaonkar@apm.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.