WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] 2.6.37 dom0 under Xen 4.1 clocksource not working

To: Daniel De Graaf <dgdegra@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] 2.6.37 dom0 under Xen 4.1 clocksource not working
From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date: Wed, 26 Jan 2011 17:07:27 +0000
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 26 Jan 2011 09:07:39 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4D4047A0.6070803@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4D2B206B.3010707@xxxxxxxxxxxxx> <4D40407F.6000108@xxxxxxxx> <4D4047A0.6070803@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Alpine 2.00 (DEB 1167 2008-08-23)
On Wed, 26 Jan 2011, Daniel De Graaf wrote:
> On 01/26/2011 10:40 AM, Jeremy Fitzhardinge wrote:
> > On 01/10/2011 07:06 AM, Daniel De Graaf wrote:
> >> When booting 2.6.37 (from kernel.org) under Xen 4.1, there are
> >> apparently issues with timer interrupts being delivered to the dom0.
> >> Repeatedly causing an interrupt (for example, the ACPI power button) will
> >> allow the system to boot, as does adding "clocksource=jiffies" to the
> >> kernel command line. This is only present under Xen, not when booting the
> >> same kernel on real hardware.
> > 
> > Ah, yes.  This is from the cpuidle stuff, I think.  Does booting with
> > "idle=halt" work?
> > 
> 
> Yes, clocksource=xen idle=halt works.

I have a testbox that can reproduce this problem.
It seems to be caused by the cpuidle driver that overrides pm_idle
unless boot_option_idle_override is set to something other than the
default.
This patch fixes the problem for me:

---

diff --git a/arch/x86/xen/setup.c b/arch/x86/xen/setup.c
index a3d28a1..7e85979 100644
--- a/arch/x86/xen/setup.c
+++ b/arch/x86/xen/setup.c
@@ -353,6 +353,7 @@ void __init xen_arch_setup(void)
        boot_cpu_data.hlt_works_ok = 1;
 #endif
        pm_idle = default_idle;
+       boot_option_idle_override = IDLE_HALT;
 
        fiddle_vdso();
 }

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel