All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Julien Grall <julien.grall@linaro.org>
Cc: xen-devel@lists.xenproject.org, tim@xen.org,
	stefano.stabellini@citrix.com
Subject: Re: [PATCH v2] xen/arm: Blacklist the memory mapped timer (armv7-timer-mem)
Date: Thu, 15 Jan 2015 15:13:38 +0000	[thread overview]
Message-ID: <1421334818.5437.20.camel@citrix.com> (raw)
In-Reply-To: <1421258443-15333-1-git-send-email-julien.grall@linaro.org>

On Wed, 2015-01-14 at 18:00 +0000, Julien Grall wrote:
> Some platform (such as the VFP Base AEMv8 model) has a memory mapped
> timer. We don't want DOM0 use this timer rather than the generic ARM
> timer. So blacklist it for all platforms.
> 
> Signed-off-by: Julien Grall <julien.grall@linaro.org>

Acked + applied.

> 
> ---
>     This patch is candidate to backport for Xen 4.5 and Xen 4.4.
> 
>     It may not apply correctly for Xen 4.4.
> 
>     Changes in v2:
>         - Add a comment in the code to explain why we need to blacklist
>         memory mapped timer
> ---
>  xen/arch/arm/domain_build.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/xen/arch/arm/domain_build.c b/xen/arch/arm/domain_build.c
> index bf8dc78..d5959b5 100644
> --- a/xen/arch/arm/domain_build.c
> +++ b/xen/arch/arm/domain_build.c
> @@ -1047,6 +1047,8 @@ static int handle_node(struct domain *d, struct kernel_info *kinfo,
>          DT_MATCH_COMPATIBLE("arm,psci"),
>          DT_MATCH_PATH("/cpus"),
>          DT_MATCH_TYPE("memory"),
> +        /* The memory mapped timer is not supported by Xen. */
> +        DT_MATCH_COMPATIBLE("arm,armv7-timer-mem"),
>          { /* sentinel */ },
>      };
>      static const struct dt_device_match gic_matches[] __initconst =

      reply	other threads:[~2015-01-15 15:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-14 18:00 [PATCH v2] xen/arm: Blacklist the memory mapped timer (armv7-timer-mem) Julien Grall
2015-01-15 15:13 ` 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=1421334818.5437.20.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=julien.grall@linaro.org \
    --cc=stefano.stabellini@citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xenproject.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.