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: "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: Tue, 30 Jan 2007 10:08:49 +0000
Delivery-date: Tue, 30 Jan 2007 02:08:30 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <D470B4E54465E3469E2ABBC5AFAC390F9E117F@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: AcdESFqDCWsISfq5RGeHgxcxVzRqmQACelaDAAAZiDAAAP4q2w==
Thread-topic: [Xen-devel] [PATCH] Fix softlockup issue after vcpu hotplug
User-agent: Microsoft-Entourage/11.2.5.060620
On 30/1/07 09:54, "Tian, Kevin" <kevin.tian@xxxxxxxxx> wrote:

> If we don't take into account blocked time, maybe we have to disable
> softlockup check. Say an idle process gets a timeout value larger than
> 10s by next_timer_interrupt, and then blocked. If, unfortunately, there's
> no other events happening before that timeout value, this vcpu will see
> softlockup warning after that timeout immediately since this period is
> not categorized into stolen time.

Presumably softlockup threads are killed and re-created when VCPUs are
offlined and onlined. Perhaps the re-creation is taking a long time? But 10s
would be a *very* long time. And once it is created and bound to the correct
VCPU we should never see long timeouts when blocking (since softlockup
thread timeout is never longer than a few seconds).

Perhaps there is a bug in our cpu onlining code -- a big timeout like that
does need investigating. I don't think we can claim this bug is root-caused
yet so it's premature to be applying patches.

 -- Keir



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