On Sun, 2014-03-16 at 22:00 -0700, Joe Perches wrote:
> On Mon, 2014-03-17 at 14:25 +1030, Rusty Russell wrote:
>
> > Erk, our tests are insufficient. Testbuilding an allmodconfig with this
> > now:
>
> Good idea.
>
> > diff --git a/include/linux/moduleparam.h b/include/linux/moduleparam.h
> []
On Mar 17, 2014, at 8:43 AM, Ronen Hod wrote:
> On 03/13/2014 09:28 AM, Jason Wang wrote:
>> On 03/10/2014 04:03 PM, Michael S. Tsirkin wrote:
>>> On Fri, Mar 07, 2014 at 01:28:27PM +0800, Jason Wang wrote:
> We used to stop the handling of tx when the number of pending DMAs
> exceeds VH
On Mar 17, 2014, at 8:43 AM, Ronen Hod wrote:
> On 03/13/2014 09:28 AM, Jason Wang wrote:
>> On 03/10/2014 04:03 PM, Michael S. Tsirkin wrote:
>>> On Fri, Mar 07, 2014 at 01:28:27PM +0800, Jason Wang wrote:
> We used to stop the handling of tx when the number of pending DMAs
> exceeds VH
On 03/13/2014 09:57 AM, Peter Zijlstra wrote:
On Wed, Mar 12, 2014 at 03:08:24PM -0400, Waiman Long wrote:
On 03/12/2014 02:54 PM, Waiman Long wrote:
+ /*
+* Set the lock bit& clear the waiting bit simultaneously
+* It is assumed that there is no
On 03/14/2014 04:30 AM, Peter Zijlstra wrote:
On Thu, Mar 13, 2014 at 04:05:19PM -0400, Waiman Long wrote:
On 03/13/2014 11:15 AM, Peter Zijlstra wrote:
On Wed, Mar 12, 2014 at 02:54:52PM -0400, Waiman Long wrote:
+static inline void arch_spin_lock(struct qspinlock *lock)
+{
+ if (static
On 03/14/2014 04:42 AM, Paolo Bonzini wrote:
Il 13/03/2014 20:13, Waiman Long ha scritto:
This should also disable the unfair path.
Paolo
The unfair lock uses a different jump label and does not require any
special PV ops. There is a separate init function for that.
Yeah, what I mean is
On Mon, Mar 17, 2014 at 01:44:34PM -0400, Waiman Long wrote:
> The PV ticketlock code was designed to handle lock holder preemption by
> redirecting CPU resources in a preempted guest to another guest that can
> better use it and then return the preempted CPU back sooner.
But that's the PV code, n
On Thu, Mar 13, 2014 at 02:16:06PM +0100, Paolo Bonzini wrote:
> Il 13/03/2014 11:54, David Vrabel ha scritto:
> >On 12/03/14 18:54, Waiman Long wrote:
> >>Locking is always an issue in a virtualized environment as the virtual
> >>CPU that is waiting on a lock may get scheduled out and hence block
On Mon, Mar 17, 2014 at 01:44:34PM -0400, Waiman Long wrote:
> On 03/14/2014 04:30 AM, Peter Zijlstra wrote:
> >On Thu, Mar 13, 2014 at 04:05:19PM -0400, Waiman Long wrote:
> >>On 03/13/2014 11:15 AM, Peter Zijlstra wrote:
> >>>On Wed, Mar 12, 2014 at 02:54:52PM -0400, Waiman Long wrote:
> +sta
