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: [PATCH][RESEND]RE: [Xen-devel] [PATCH] Fix softlockup issue after vc

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [PATCH][RESEND]RE: [Xen-devel] [PATCH] Fix softlockup issue after vcpu hotplug
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Fri, 2 Feb 2007 10:48:31 +0800
Delivery-date: Thu, 01 Feb 2007 18:48:21 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C1E84D2E.8BDF%Keir.Fraser@xxxxxxxxxxxx>
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: AcdESFqDCWsISfq5RGeHgxcxVzRqmQACelaDAAAZiDAAAP4q2wADxf1QAAFVV3AAAMUYXAAACCkwAACFZyAAAV9OMAABEoucACBxTEAATS41lQANfeFwAACGefIAAJFJTQAA88jJAAFt7gA=
Thread-topic: [PATCH][RESEND]RE: [Xen-devel] [PATCH] Fix softlockup issue after vcpu hotplug
>From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx]
>Sent: 2007年2月2日 10:07
>
>Okay, I now see how this works -- the thread is kicked from
>softlockup_tick(), from the timer ISR. So this wakeup event is hidden
>from
>next_timer_interrupt(), which only searches timer wheels and hrtimers.

Exactly.

>
>The strictly correct fix here is to make next_timer_interrupt()
>softlockup-aware. I would say it is currently incorrect in the presence of
>softlockup since it is not doing its job (telling an idle process what the
>next time-based event is that it must wake up for).
>
>We can do this by adding a softlockup_get_next_event(), called from the
>bottom of next_timer_interrupt(). I would pass it the current return value
>and have it return an adjusted value: so in the absence of softlockup it
>would simply return its argument unmodified. In the presence of
>softlockup
>it would return a sooner value if softlockup is the next event to fire.
>
>Do you want to try coding this up?
>
> -- Keir

Sure.

Thanks,
Kevin

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