Re: [kvm-devel] KVM Test result, kernel 873c05f.., userspace d102d75..

Marcelo Tosatti wrote: > On Thu, Apr 24, 2008 at 04:44:27PM +0300, Avi Kivity wrote: > >> Chris Lalancette wrote: >> >>> Avi Kivity wrote: >>> >>> Ok. __pit_timer_fn() is called from an interrupt, which then calls smp_call_function_single(), which calls spin_lock(). If

Re: [kvm-devel] KVM Test result, kernel 873c05f.., userspace d102d75..

On Thu, Apr 24, 2008 at 04:44:27PM +0300, Avi Kivity wrote: > Chris Lalancette wrote: > >Avi Kivity wrote: > > > >>Ok. __pit_timer_fn() is called from an interrupt, which then calls > >>smp_call_function_single(), which calls spin_lock(). If we've already > >>taken the lock, we hang. > >> > >

Re: [kvm-devel] KVM Test result, kernel 873c05f.., userspace d102d75..

Chris Lalancette wrote: > Avi Kivity wrote: > >> Ok. __pit_timer_fn() is called from an interrupt, which then calls >> smp_call_function_single(), which calls spin_lock(). If we've already >> taken the lock, we hang. >> >> > > Ah. Just adding a "me too"; I didn't get a chance to debug

Re: [kvm-devel] KVM Test result, kernel 873c05f.., userspace d102d75..

Avi Kivity wrote: > > Ok. __pit_timer_fn() is called from an interrupt, which then calls > smp_call_function_single(), which calls spin_lock(). If we've already > taken the lock, we hang. > Ah. Just adding a "me too"; I didn't get a chance to debug it yesterday, but I was seeing similar pro

Re: [kvm-devel] KVM Test result, kernel 873c05f.., userspace d102d75..

Avi Kivity wrote: > Yang, Sheng wrote: >> On Thursday 24 April 2008 19:37:03 Avi Kivity wrote: >> >>> Yunfeng Zhao wrote: >>> Hi All, This is today's KVM test result against kvm.git 873c05fa7e6fea27090b1bf0f67a073eadb04782 and kvm-userspace.git d102d750f397b543fe620a3

Re: [kvm-devel] KVM Test result, kernel 873c05f.., userspace d102d75..

Yang, Sheng wrote: > On Thursday 24 April 2008 19:37:03 Avi Kivity wrote: > >> Yunfeng Zhao wrote: >> >>> Hi All, >>> >>> This is today's KVM test result against kvm.git >>> 873c05fa7e6fea27090b1bf0f67a073eadb04782 and kvm-userspace.git >>> d102d750f397b543fe620a3c77a7e5e42c483865. >>>

Re: [kvm-devel] KVM Test result, kernel 873c05f.., userspace d102d75..

On Thursday 24 April 2008 19:37:03 Avi Kivity wrote: > Yunfeng Zhao wrote: > > Hi All, > > > > This is today's KVM test result against kvm.git > > 873c05fa7e6fea27090b1bf0f67a073eadb04782 and kvm-userspace.git > > d102d750f397b543fe620a3c77a7e5e42c483865. > > I suspect 873c05fa7e6fea27090b1bf0f67a0

Re: [kvm-devel] KVM Test result, kernel 873c05f.., userspace d102d75..

Yunfeng Zhao wrote: > Hi All, > > This is today's KVM test result against kvm.git > 873c05fa7e6fea27090b1bf0f67a073eadb04782 and kvm-userspace.git > d102d750f397b543fe620a3c77a7e5e42c483865. > > I suspect 873c05fa7e6fea27090b1bf0f67a073eadb04782 itself, it's the only thing that has any cha

[kvm-devel] KVM Test result, kernel 873c05f.., userspace d102d75..

Hi All, This is today's KVM test result against kvm.git 873c05fa7e6fea27090b1bf0f67a073eadb04782 and kvm-userspace.git d102d750f397b543fe620a3c77a7e5e42c483865. In today's nightly testing, we meet host hang while booting multiple guests several times. This issue could be easily reproduced.