Re: [Xen-devel] Biweekly VMX status report. Xen: #21438 & Xen0: #a3e7c7...

[Keir Fraser <keir.fraser@xxxxxxxxxxxxx>]

On 02/06/2010 08:28, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx> wrote:

>> Which xen-unstable changeset are you testing? All timers should be
>> automatically migrated off a dead CPU and onto CPU0 by changeset 21424. Is
>> that not working okay for you?
> 
> We are testing on 21492.
> 
> After more investigation, the root cause is the periodic_timer is stopped
> before take_cpu_down (in schedule()), so that it is not covred by 21424.
> When v->periodic_period ==0, next vcpu's p_timer is not updated by the
> schedule(), thus, later in next schedule round, it will cause trouble for
> stop_timer().
> 
> With following small patch, it works, but I'm not sure if this is good
> solution.

I forgot about inactive timers in c/s 21424. Hm, I will fix this in the
timer subsystem and get back to you.

 -- Keir



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