From: Ian Campbell <ian.campbell@citrix.com>
To: Julien Grall <julien.grall@citrix.com>
Cc: wei.liu2@citrix.com, ian.jackson@eu.citrix.com, tim@xen.org,
stefano.stabellini@citrix.com,
Chris Brand <chris.brand@broadcom.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH] xen/arm: Propagate clock-frequency to DOMU if present in the DT timer node
Date: Wed, 17 Jun 2015 11:57:39 +0100 [thread overview]
Message-ID: <1434538659.13744.320.camel@citrix.com> (raw)
In-Reply-To: <1433342886-14790-1-git-send-email-julien.grall@citrix.com>
On Wed, 2015-06-03 at 15:48 +0100, Julien Grall wrote:
> When the property "clock-frequency" is present in the DT timer node, it
> means that the bootloader/firmware didn't correctly configured the
"configure"
> CNTFRQ/CNTFRQ_EL0 on each processor.
>
> The best solution would be to fix the offending firmware/bootloader,
> although it may not always be possible to modify and re-flash it.
>
> As it's not possible to trap the register CNTFRQ/CNTFRQ_EL0, we have
> to extend xen_arch_domainconfig to provide the timer frequency to the
> toolstack when the property "clock-frequency" is present to the host DT
> timer node. Then, a property "clock-frequency" will be created in the guest
> DT timer node if the value is not 0.
>
> We could have set the property in the guest DT no matter if the property
> is present in the host DT. Although, we still want to let the guest
> using CNTFRQ in normal case. After all, the property "clock-frequency"
> is just a workaround for buggy firmware.
>
> Signed-off-by: Julien Grall <julien.grall@citrix.com>
> Cc: Chris Brand <chris.brand@broadcom.com>
I was about to apply but:
libxl_arm.c: In function ‘make_timer_node’:
libxl_arm.c:468:9: error: implicit declaration of function ‘fdt_property_u32’ [-Werror=implicit-function-declaration]
cc1: all warnings being treated as errors
That happen on both my 32 bit build (Debian Wheezy) and my 64 bit on
(Ubuntu Saucy).
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-06-17 11:18 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
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 [this message]
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=1434538659.13744.320.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=chris.brand@broadcom.com \
--cc=ian.jackson@eu.citrix.com \
--cc=julien.grall@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.