[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH 9/9] qspinlock, x86, kvm: Implement KVM support for paravirt qspinlock
- To: Waiman Long <waiman.long@xxxxxx>
- From: Raghavendra K T <raghavendra.kt@xxxxxxxxxxxxxxxxxx>
- Date: Fri, 20 Mar 2015 13:13:56 +0530
- Cc: linux-arch@xxxxxxxxxxxxxxx, riel@xxxxxxxxxx, kvm@xxxxxxxxxxxxxxx, Peter Zijlstra <peterz@xxxxxxxxxxxxx>, scott.norton@xxxxxx, x86@xxxxxxxxxx, paolo.bonzini@xxxxxxxxx, oleg@xxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, mingo@xxxxxxxxxx, david.vrabel@xxxxxxxxxx, hpa@xxxxxxxxx, luto@xxxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxxx, tglx@xxxxxxxxxxxxx, paulmck@xxxxxxxxxxxxxxxxxx, torvalds@xxxxxxxxxxxxxxxxxxxx, boris.ostrovsky@xxxxxxxxxx, virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx, doug.hatch@xxxxxx
- Delivery-date: Fri, 20 Mar 2015 08:02:09 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
On 03/20/2015 02:38 AM, Waiman Long wrote:
On 03/19/2015 06:01 AM, Peter Zijlstra wrote:
[...]
You are probably right. The initial apply_paravirt() was done before the
SMP boot. Subsequent ones were at kernel module load time. I put a
counter in the __native_queue_spin_unlock() and it registered 26949
unlock calls in a 16-cpu guest before it got patched out.
because even printks take lock..
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
