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: Mon, 17 Mar 2014 13:52:27 +0000 [thread overview]
Message-ID: <5326FE1B.3080800@linaro.org> (raw)
In-Reply-To: <CANoR_ODxC=Cdm7Fudrp5GCHe04NcEzWfHJLbSARK5NDTTgLNxg@mail.gmail.com>
On 03/17/2014 01:32 PM, Suriyan Ramasami wrote:
> On Mon, Mar 17, 2014 at 6:21 AM, Julien Grall <julien.grall@linaro.org> wrote:
>> Hello Suriyan,
>>
>> On 03/17/2014 01:17 PM, Suriyan Ramasami wrote:
>>> On Sun, Mar 16, 2014 at 1:31 PM, Julien Grall <julien.grall@citrix.com> wrote:
>>>> Can you post the modification you made? (at least where does the print come
>>>> from).
>>> The boot_count print is coming from a mod in xen/arch/arm/time.c in
>>> function init_xen_time()
>>> - printk("boot_count: %llu reread: %llu\n", boot_count,
>>> READ_SYSREG64(CNTPCT_EL0));
>>> just before the function returns. The timer is started up in u-boot.
>>> All the other printfs that you see with "Calling" is at the start of
>>> the fucntions - I was trying to figure out if xen was hanging - this
>>> is not the case though.
>>>
>>> I shall reply further on Ian's email where I do see dom0 hanging in
>>> calibrate_delay(). If I pass lpj=4464640 in the kernel parameters, it
>>> then loops in do_xor_speed() - specifically in the line while ((now =
>>> jiffies) == j), which points to jiffies not getting incremented at
>>> all!
>>
>> I remembered to have the same issue with Arndale a while ago. Which
>> kernel are you using? Can you give the dom0 log?
>>
> I am using linux kernel 3.13 which boots without xen. With xen, I do
By 3.13, you mean https://github.com/hardkernel/linux.git branch
odroid-3.13.y-linaro, right?
> not see any dom0 output (I even added the patch that you suggested in
> http://lists.xen.org/archives/html/xen-devel/2013-04/msg02387.html) -
> still no output from dom0.
> I am pasting the linux output without xen, if that helps:
Hmmm ... the exynos 5250 has it's own timer (samsung,exynos4210-mct)
which shouldn't be passthrough to dom0. I suspect that your issue come
from there.
Did you add specific platform code for the board? Can you uncomment
#define DEBUG_DT in xen/arch/arm/domain_build.c and paste the log on
pastebin?
Thanks,
--
Julien Grall
next prev parent reply other threads:[~2014-03-17 13:52 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 [this message]
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
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=5326FE1B.3080800@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.