From: Julien Grall <julien.grall@citrix.com>
To: "Chris (Christopher) Brand" <chris.brand@broadcom.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "ian.jackson@eu.citrix.com" <ian.jackson@eu.citrix.com>,
"stefano.stabellini@citrix.com" <stefano.stabellini@citrix.com>,
"tim@xen.org" <tim@xen.org>,
"ian.campbell@citrix.com" <ian.campbell@citrix.com>,
"wei.liu2@citrix.com" <wei.liu2@citrix.com>
Subject: Re: [PATCH] xen/arm: Propagate clock-frequency to DOMU if present in the DT timer node
Date: Thu, 4 Jun 2015 00:24:03 +0100 [thread overview]
Message-ID: <556F8C93.4000703@citrix.com> (raw)
In-Reply-To: <4EE5B48738DDED408878C97C8E050A8B1D7A3B47@SJEXCHMB05.corp.ad.broadcom.com>
On 03/06/2015 23:45, Chris (Christopher) Brand wrote:
> Hi Julien,
Hi Chris,
>> When the property "clock-frequency" is present in the DT timer node, it means that the bootloader/firmware didn't correctly configured the
>> CNTFRQ/CNTFRQ_EL0 on each processor.
> I will test this patch, but it doesn't apply cleanly to the version of Xen I'm currently using, so I need to update that first.
It's based on the latest staging.
> I also looked at whether it would be possible to set the CNTFRQ register in the other cores when they come up. Eventually, I think we should do this in the (platform-specific) PSCI code. There doesn't seem to be a suitable hook in the platform-specific Xen code - it looks like all the code there related to bringing up secondary cores runs on the primary.
CNTFRQ is read-only in the hypervisor when the platform supports EL3
(i.e secure monitor).
So it has to be done either by the bootloader or by the firmware.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2015-06-03 23:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 14:48 [PATCH] xen/arm: Propagate clock-frequency to DOMU if present in the DT timer node Julien Grall
2015-06-03 22:45 ` Chris (Christopher) Brand
2015-06-03 23:24 ` Julien Grall [this message]
2015-06-05 20:14 ` Chris (Christopher) Brand
2015-06-07 21:04 ` Julien Grall
2015-06-08 20:44 ` Chris (Christopher) Brand
2015-06-09 23:48 ` Julien Grall
2015-06-10 17:42 ` Julien Grall
2015-06-10 21:41 ` Chris (Christopher) Brand
2015-06-11 21:43 ` Chris (Christopher) Brand
2015-06-12 11:42 ` Julien Grall
2015-06-12 15:16 ` Chris (Christopher) Brand
2015-06-17 10:57 ` Ian Campbell
2015-06-17 12:49 ` Julien Grall
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=556F8C93.4000703@citrix.com \
--to=julien.grall@citrix.com \
--cc=chris.brand@broadcom.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--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.