From: Julien Grall <julien.grall@linaro.org>
To: Suriyan Ramasami <suriyan.r@gmail.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>, xen-devel@lists.xen.org
Subject: Re: ARM: EXYNOS 5410 - DOM0 not being scheduled
Date: Tue, 18 Mar 2014 16:09:21 +0000 [thread overview]
Message-ID: <53286FB1.9010501@linaro.org> (raw)
In-Reply-To: <CANoR_OBmM8H0ho9sjzTpbnH6BPTxV3brKpad689eOKGRjrjOsw@mail.gmail.com>
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
next prev parent reply other threads:[~2014-03-18 16:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-15 14:44 ARM: EXYNOS 5410 - DOM0 not being scheduled Suriyan Ramasami
2014-03-16 20:31 ` Julien Grall
2014-03-17 13:17 ` Suriyan Ramasami
2014-03-17 13:21 ` Julien Grall
2014-03-17 13:32 ` Suriyan Ramasami
2014-03-17 13:52 ` Julien Grall
2014-03-17 17:39 ` Suriyan Ramasami
2014-03-17 18:10 ` Suriyan Ramasami
2014-03-17 18:22 ` Suriyan Ramasami
2014-03-17 22:15 ` Julien Grall
2014-03-18 9:52 ` Ian Campbell
2014-03-18 12:04 ` Julien Grall
2014-03-18 13:37 ` Ian Campbell
2014-03-18 15:41 ` Suriyan Ramasami
2014-03-18 16:09 ` Julien Grall [this message]
2014-03-17 22:03 ` Julien Grall
2014-03-17 10:09 ` Ian Campbell
2014-03-17 13:24 ` Suriyan Ramasami
2014-03-17 13:36 ` 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=53286FB1.9010501@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=suriyan.r@gmail.com \
--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.