[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH] x86 spinlock: Fix memory corruption on completing completions
- To: Raghavendra K T <raghavendra.kt@xxxxxxxxxxxxxxxxxx>, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Davidlohr Bueso <dave@xxxxxxxxxxxx>
- From: Sasha Levin <sasha.levin@xxxxxxxxxx>
- Date: Tue, 10 Feb 2015 08:23:10 -0500
- Cc: KVM list <kvm@xxxxxxxxxxxxxxx>, Peter Zijlstra <peterz@xxxxxxxxxxxxx>, Jason Wang <jasowang@xxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Paul Gortmaker <paul.gortmaker@xxxxxxxxxxxxx>, Peter Anvin <hpa@xxxxxxxxx>, Andi Kleen <ak@xxxxxxxxxxxxxxx>, Andrey Ryabinin <a.ryabinin@xxxxxxxxxxx>, the arch/x86 maintainers <x86@xxxxxxxxxx>, Christian Borntraeger <borntraeger@xxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx, Paul McKenney <paulmck@xxxxxxxxxxxxxxxxxx>, Dave Jones <davej@xxxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, virtualization <virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx>, Waiman Long <waiman.long@xxxxxx>, Oleg Nesterov <oleg@xxxxxxxxxx>, Paolo Bonzini <pbonzini@xxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
- Delivery-date: Tue, 10 Feb 2015 13:24:19 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
On 02/10/2015 04:30 AM, Raghavendra K T wrote:
>>
>> So I think Raghavendra's last version (which hopefully fixes the
>> lockup problem that Sasha reported) together with changing that
>
> V2 did pass the stress, but getting confirmation Sasha would help.
I've been running it for the last two days, and didn't see any lockups
or other strange behaviour aside from some invalid reads which we
expected.
Thanks,
Sasha
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
