From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: ARM: EXYNOS 5410 - DOM0 not being scheduled Date: Mon, 17 Mar 2014 13:52:27 +0000 Message-ID: <5326FE1B.3080800@linaro.org> References: <53260A3D.5080202@citrix.com> <5326F6CC.3060303@linaro.org> 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 On 03/17/2014 01:32 PM, Suriyan Ramasami wrote: > On Mon, Mar 17, 2014 at 6:21 AM, Julien Grall wrote: >> Hello Suriyan, >> >> On 03/17/2014 01:17 PM, Suriyan Ramasami wrote: >>> On Sun, Mar 16, 2014 at 1:31 PM, Julien Grall 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