On 24/06/2015 19:07, John Nielsen wrote:
>
> Unfortunately I no longer have the test environment I used a few days
> ago to reproduce this issue so I can’t verify the software versions
> that were in use. It’s possible I was mistaken about the kernel
> version (I thought it was 4.0.4). Perhaps it really is fixed in the
> newer kernel? In any case, this is great news! I would be interested
> in identifying the patch(es) that fixed the issue to make
> back-porting them easier, but I won’t have time to do a binary search
> anytime soon.
Random guess:
commit a323b409820c8afd33fbd841f5534eb84b406e8d
Author: Radim Krčmář <rkrcmar@xxxxxxxxxx>
Date: Thu Oct 30 15:06:46 2014 +0100
KVM: x86: detect LVTT changes under APICv
commit e462755cae2bf8297a663278935ad4d59812d2f3
Author: Radim Krčmář <rkrcmar@xxxxxxxxxx>
Date: Thu Oct 30 15:06:45 2014 +0100
KVM: x86: detect SPIV changes under APICv
Paolo
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
