Re: KVM: Remaining body of TSC emulation work

[Zachary Amsden <zamsden@redhat.com>]

On 06/21/2011 01:50 AM, Jan Kiszka wrote:
> On 2011-06-21 01:59, Zachary Amsden wrote:
>    
>> In-Reply-To:
>>
>> This is the remaining bulk of work I have related to TSC emulation.
>> In summary, I believe this fixes all known issues with TSC.  A few
>> rather subtle issues are cleaned up, S4 suspend is fixed, and the
>> API for adjust_tsc_offset is expanded to take arguments in either
>> guest cycles or optionally host cycles.  The final patch adds
>> software TSC emulation, with a configurable default setting.
>>
>> Note that TSC trapping will only be used when other methods fail
>> due to unstable TSC or lack of scaling hardware.  With the improved
>> offset matching, I was even able to get SMP guests to boot with a
>> TSC clock; cycle testing showed a maximum backwards leap of around
>> 0.25 ms, which is actually fairly good.  With the last patch applied,
>> software TSC emulation kicks in and the backwards TSC count even on
>> my broken hardware dropped to zero.
>>
>> Some of this code (the S4 suspend compensation) has already been
>> ported into RHEL to fix various bugs - however upstream had diverged
>> a bit from the original course I planned; I had to add a few things
>> that had been optimized out of upstream back in (last_host_tsc).
>>
>> In the course of doing this, I think the new code looks much
>> cleaner, with well documented and easy to understand variables.
>> Yes, there are a lot of tracking variables to maintain this whole
>> infrastructure - and yes, some of them appear to be redundant of
>> easily computable from others - but in actuality, the information
>> they provide is easy to understand, and the resulting code is much
>> easier to verify than a complex system where some quantities may
>> be undefined or computed on the fly and thus causing subtle races.
>>
>> Zach
>>
>>      
> You want this to show up on kvm@vger.kernel.org as well, no? :)
>    

Yeah, oops on that.

> Looks like there is still mark_tsc_unstable in KVM code, so we aren't
> yet at the point of ultimate cleanness. Nevertheless, we see that I'll
> test suspend to RAM with this soon.
>    

Yeah, I decided not to remove it... should it fire, we've detected 
either a bad hardware TSC or some previously unseen platform behavior.  
We're obligated to report it, and if it turns out to be another issue 
like suspend to RAM, we now have the machinery to fix it.

Zach