All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>, xen-devel@lists.xen.org
Cc: julien.grall@citrix.com, tim@xen.org, stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH] xen: arm: Do not expose PMU to domain 0
Date: Fri, 5 Jun 2015 11:17:28 +0100	[thread overview]
Message-ID: <55717738.60005@citrix.com> (raw)
In-Reply-To: <1433436583-19676-1-git-send-email-ian.campbell@citrix.com>

Hi Ian,

On 04/06/2015 17:49, Ian Campbell wrote:
> It uses a PPI which we cannot route to a guest, and will surely need
> more support than just that anyway.
>
> I noticed this on Mustang with UEFI where the built in DTB contains a
> node of this type.
>
> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> ---
>   xen/arch/arm/domain_build.c |    1 +
>   1 file changed, 1 insertion(+)
>
> diff --git a/xen/arch/arm/domain_build.c b/xen/arch/arm/domain_build.c
> index 1e545fe..8e87315 100644
> --- a/xen/arch/arm/domain_build.c
> +++ b/xen/arch/arm/domain_build.c
> @@ -1105,6 +1105,7 @@ static int handle_node(struct domain *d, struct kernel_info *kinfo,
>           DT_MATCH_COMPATIBLE("multiboot,module"),
>           DT_MATCH_COMPATIBLE("arm,psci"),
>           DT_MATCH_COMPATIBLE("arm,psci-0.2"),
> +        DT_MATCH_COMPATIBLE("arm,armv8-pmuv3"),

Will you are here, can you blacklist at list "arm,cortex-a15-pmu" and 
"arm,cortex-a7-pmu"?

I suspect we would have the same problem with them.

Regards,

-- 
Julien Grall

  reply	other threads:[~2015-06-05 10:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04 16:49 [PATCH] xen: arm: Do not expose PMU to domain 0 Ian Campbell
2015-06-05 10:17 ` Julien Grall [this message]
2015-06-05 10:25   ` Ian Campbell
2015-06-05 11:20     ` Julien Grall
2015-06-05 11:39       ` 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=55717738.60005@citrix.com \
    --to=julien.grall@citrix.com \
    --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.