From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xenproject.org, tim@xen.org,
stefano.stabellini@citrix.com
Subject: Re: [PATCH] xen/arm: Blacklist the memory mapped timer (armv7-timer-mem)
Date: Wed, 14 Jan 2015 16:03:53 +0000 [thread overview]
Message-ID: <54B69369.6000707@linaro.org> (raw)
In-Reply-To: <1421233321.19103.215.camel@citrix.com>
Hi Ian,
On 14/01/15 11:02, Ian Campbell wrote:
> On Tue, 2015-01-13 at 20:07 +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.
>
> It seems that these registers contain things like the ability to stop
> the counter or change its frequency. So we certainly don't want dom0
> getting at those!
>
> It's not clear to me if accesses to these registers are trapped
> according to the controls available for the CP registers, or if we would
> have to resort to trapping the entire MMIO page if we wanted to support
> access to these registers (I don't think we would want to anyway).
I didn't find any spec for the memory mapped timer. But looking to the
driver, it looks like they also have the concept of physical/virtual. So
we may not need to trap.
Anyway, before implementing anything I'd like to find the corresponding
spec.
>> Signed-off-by: Julien Grall <julien.grall@linaro.org>
>>
>> ---
>> This patch is candidate to backport for Xen 4.5 and Xen 4.4.
>>
>> It may not apply correctly for Xen 4.4.
>> ---
>> 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 bf8dc78..16ce248 100644
>> --- a/xen/arch/arm/domain_build.c
>> +++ b/xen/arch/arm/domain_build.c
>> @@ -1047,6 +1047,7 @@ static int handle_node(struct domain *d, struct kernel_info *kinfo,
>> DT_MATCH_COMPATIBLE("arm,psci"),
>> DT_MATCH_PATH("/cpus"),
>> DT_MATCH_TYPE("memory"),
>> + DT_MATCH_COMPATIBLE("arm,armv7-timer-mem"),
>
> This is a bit less obvious that the other things in this list. Could you
> perhaps add a comment?
Sure. I will send a new version.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2015-01-14 16:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 20:07 [PATCH] xen/arm: Blacklist the memory mapped timer (armv7-timer-mem) Julien Grall
2015-01-14 11:02 ` Ian Campbell
2015-01-14 16:03 ` Julien Grall [this message]
2015-01-14 16:06 ` 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=54B69369.6000707@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--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.