From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Magenheimer Subject: RE: [timer/ticks related] dom0 hang during boot on large 1TB system Date: Mon, 21 Dec 2009 15:57:33 -0800 (PST) Message-ID: References: <4B300120.4040405@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=Windows-1252 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <4B300120.4040405@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Fitzhardinge , mukesh.rathor@oracle.com Cc: kurt.hackel@oracle.com, Xen-devel@lists.xensource.com, Keir Fraser , Jan Beulich List-Id: xen-devel@lists.xenproject.org > From: Jeremy Fitzhardinge [mailto:jeremy@goop.org] > > There's some code in the pvops kernel which looks vaguely=20 > like that, but=20 > it has nothing to do with timer interrupts. Could you be=20 > more specific=20 > about what you're referring to? I spent some time rooting through the 2.6.32 code and ended up with my head spinning. I think the bottom line is if there is code that may cause jiffies to increment by a large amount from a single "tick" delivered by Xen, it's likely the same problem can occur in 2.6.32 dom0 when running on Xen.