Re: [PATCH] i386/kvm: correct the meaning of '0xffffffff' value for hv-spinlocks

2020-07-21 Thread Vitaly Kuznetsov
Eduardo Habkost writes: > On Fri, May 15, 2020 at 01:48:47PM +0200, Vitaly Kuznetsov wrote: >> Hyper-V TLFS prior to version 6.0 had a mistake in it: special value >> '0x' for CPUID 0x4004.EBX was called 'never to retry', this >> looked weird (like why it's not '0' which supposedly ha

Re: [PATCH] i386/kvm: correct the meaning of '0xffffffff' value for hv-spinlocks

2020-07-20 Thread Eduardo Habkost
On Fri, May 15, 2020 at 01:48:47PM +0200, Vitaly Kuznetsov wrote: > Hyper-V TLFS prior to version 6.0 had a mistake in it: special value > '0x' for CPUID 0x4004.EBX was called 'never to retry', this > looked weird (like why it's not '0' which supposedly have the same effect?) > but nobo

[PATCH] i386/kvm: correct the meaning of '0xffffffff' value for hv-spinlocks

2020-05-15 Thread Vitaly Kuznetsov
Hyper-V TLFS prior to version 6.0 had a mistake in it: special value '0x' for CPUID 0x4004.EBX was called 'never to retry', this looked weird (like why it's not '0' which supposedly have the same effect?) but nobody raised the question. In TLFS version 6.0 the mistake was corrected to '