lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sat, 12 Dec 2020 14:03:22 +0100
From:   Thomas Gleixner <>
To:     Paolo Bonzini <>,
        Marcelo Tosatti <>
Cc:     Maxim Levitsky <>,,
        "H. Peter Anvin" <>, Jonathan Corbet <>,
        Jim Mattson <>,
        Wanpeng Li <>,
        "open list\:KERNEL SELFTEST FRAMEWORK" 
        Vitaly Kuznetsov <>,
        Sean Christopherson <>,
        open list <>,
        Ingo Molnar <>,
        "maintainer\:X86 ARCHITECTURE \(32-BIT AND 64-BIT\)" <>,
        Joerg Roedel <>, Borislav Petkov <>,
        Shuah Khan <>,
        Andrew Jones <>,
        Oliver Upton <>,
        "open list\:DOCUMENTATION" <>
Subject: Re: [PATCH v2 1/3] KVM: x86: implement KVM_{GET|SET}_TSC_STATE

On Fri, Dec 11 2020 at 22:59, Paolo Bonzini wrote:
> On 11/12/20 22:04, Thomas Gleixner wrote:
> The nanosecond and TSC times are sent as part of the paused-VM state at 
> the very end of the live migration process.
> So it's still true that the time advances during live migration 
> brownout; 0.1 seconds is just the final part of the live migration 
> process.  But for _live_ migration there is no need to design things 
> according to "people are happy if their clock is off by 0.1 seconds 
> only".

The problem is not the 0.1 second jump of the TSC. That's just a minor
nuisance. The problem is the incorrectness of CLOCK_REALTIME after this
operation which is far larger than 0.1s and this needs to be fixed.

> Again, save-to-disk, reverse debugging and the like are a different
> story, which is why KVM should delegate policy to userspace (while
> documenting how to do it right).

One ready to use option would be suspend to idle. It's fast and readily
available including all the notifications and kernel side handling of
time and whatever.



Powered by blists - more mailing lists