From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: ARM: EXYNOS 5410 - DOM0 not being scheduled Date: Tue, 18 Mar 2014 16:09:21 +0000 Message-ID: <53286FB1.9010501@linaro.org> References: <53260A3D.5080202@citrix.com> <5326F6CC.3060303@linaro.org> <5326FE1B.3080800@linaro.org> <53277409.7010900@linaro.org> <1395136344.12847.13.camel@kazak.uk.xensource.com> <5328363C.6030407@linaro.org> <1395149872.12847.51.camel@kazak.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Suriyan Ramasami Cc: Ian Campbell , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org Hi Suriyan, On 03/18/2014 03:41 PM, Suriyan Ramasami wrote: > I am also trying to fix it in the boot loader. Nonetheless, I have a > gap in my understanding as to why using clock-frequency in domU would > create a problem? > If its OK for dom0 and domU to use clock-frequency in the case that > CNTFRQ comes up as 0, I would definitely submit a patch. The problem is not using "clock-frequency" into the guest, is how to retrieve the clock frequency in libxl to correctly create the property? One solution might be browsing /proc/devicetree, but it doesn't always exists (e.g CONFIG_PROC_DEVICETREE=n). Regards -- Julien Grall