Message-ID: <1438022488.25997.40.camel@stgolabs.net>
Subject: Re: [PATCH v3 1/7] locking/pvqspinlock: Unconditional PV kick with
 _Q_SLOW_VAL
From: Davidlohr Bueso <dave@stgolabs.net>
To: Waiman Long <waiman.long@hp.com>
Cc: Peter Zijlstra <peterz@infradead.org>, Ingo Molnar <mingo@redhat.com>,
        Thomas Gleixner <tglx@linutronix.de>, "H. Peter Anvin" <hpa@zytor.com>,
        x86@kernel.org, linux-kernel@vger.kernel.org,
        Scott J Norton <scott.norton@hp.com>,
        Douglas Hatch <doug.hatch@hp.com>
Date: Mon, 27 Jul 2015 11:41:28 -0700
In-Reply-To: <55B66F83.7040105@hp.com>
References: <1437595962-21472-1-git-send-email-Waiman.Long@hp.com>
	 <1437595962-21472-2-git-send-email-Waiman.Long@hp.com>
	 <1437863509.3298.71.camel@stgolabs.net>
	 <1437961615.25997.36.camel@stgolabs.net> <55B66F83.7040105@hp.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 750
Lines: 15

On Mon, 2015-07-27 at 13:50 -0400, Waiman Long wrote:
> As for the spurious-wakeups.txt, I saw there are spurious wakeup 
> occasionally. However, I am not totally sure of the mechanism that 
> causes it. Also the spurious wakeup here refers to the vmenter of the 
> vCPU which is different from spurious wakeup of a sleeping thread. I 
> don't think I have enough data and information to write a document file yet.

Right, this was a generic idea, not only regarding actual wakeups of
sleeping threads.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/