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] [PATCH] Fix softlockup issue after vcpu hotplug

To: "Graham, Simon" <Simon.Graham@xxxxxxxxxxx>, "Tian, Kevin" <kevin.tian@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Fix softlockup issue after vcpu hotplug
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Thu, 01 Feb 2007 23:26:54 +0000
Delivery-date: Thu, 01 Feb 2007 15:28:01 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <342BAC0A5467384983B586A6B0B37671048F8F6B@xxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcdESFqDCWsISfq5RGeHgxcxVzRqmQACelaDAAAZiDAAAQnwRAATVWmwABVdeuAAQqkN4AAKff/fAAh92KAAAhEUjg==
Thread-topic: [Xen-devel] [PATCH] Fix softlockup issue after vcpu hotplug
User-agent: Microsoft-Entourage/11.2.5.060620


On 1/2/07 22:40, "Graham, Simon" <Simon.Graham@xxxxxxxxxxx> wrote:

> I also considered only touching the watchdog timer every 5s or so, but I
> think the code to do that would have more overhead than simply touching
> it for every do_timer() call (since it's just a call that copies jiffies
> to the per-cpu watchdog timer value).
> 
> Take a look and let me know what you think (the printk could be removed
> -- I just put it in so I could tell the code was running).

The test inside the loop should check against NS_PER_TICK*100, not just 0.
You only want to override the usual running of the watchdog if you get a big
bunch of time stolen from you. Actually, five seconds (NS_PER_TICK*5*HZ)
would be good: no reason to make the comparison dependent on the duration of
a jiffy.

 -- Keir



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