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

[Vitaly Kuznetsov]

Eduardo Habkost <ehabkost@redhat.com> 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
>> '0xffffffff' for CPUID 0x40000004.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 'never notify' which sounds logical. Fix QEMU accordingly.
>> 
>> Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
>
> I've just found this buried in my inbox, sorry for missing it!

Better late than never! (And, to be honest, I completely forgot about it
as well :-)

>
> Queued for 5.2.
>

Thanks!

-- 
Vitaly