On Thu, Feb 08, 2018 at 04:32:29PM +1300, Jonathan Matthew wrote:
> This diff (most of which has been around for a while) changes delay_func
> when running in KVM to use pvclock (effectively the TSC) to determine when to
> stop spinning. Since this is done in a KVM-specific driver, it won't have
>
On Thu, Feb 08, 2018 at 04:32:29PM +1300, Jonathan Matthew wrote:
> This diff (most of which has been around for a while) changes delay_func
> when running in KVM to use pvclock (effectively the TSC) to determine when to
> stop spinning. Since this is done in a KVM-specific driver, it won't have
>
On Wed, Feb 07, 2018 at 09:35:04PM -0800, Mike Larkin wrote:
> On Thu, Feb 08, 2018 at 04:32:29PM +1300, Jonathan Matthew wrote:
> > This diff (most of which has been around for a while) changes delay_func
> > when running in KVM to use pvclock (effectively the TSC) to determine when
> > to
> > st
On Thu, Feb 08, 2018 at 04:32:29PM +1300, Jonathan Matthew wrote:
> This diff (most of which has been around for a while) changes delay_func
> when running in KVM to use pvclock (effectively the TSC) to determine when to
> stop spinning. Since this is done in a KVM-specific driver, it won't have
>
On Thu, Feb 08, 2018 at 04:32:29PM +1300, Jonathan Matthew wrote:
> This diff (most of which has been around for a while) changes delay_func
> when running in KVM to use pvclock (effectively the TSC) to determine when to
> stop spinning. Since this is done in a KVM-specific driver, it won't have
>
This diff (most of which has been around for a while) changes delay_func
when running in KVM to use pvclock (effectively the TSC) to determine when to
stop spinning. Since this is done in a KVM-specific driver, it won't have
any effect anywhere other than in KVM guests.
Using pvclock rather than