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] [day] [month] [year] [list]
Date:   Tue, 15 Dec 2020 23:34:46 +0100
From:   Thomas Gleixner <>
To:     Marcelo Tosatti <>,
        Paolo Bonzini <>
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 Tue, Dec 15 2020 at 07:59, Marcelo Tosatti wrote:
> On Fri, Dec 11, 2020 at 10:59:59PM +0100, Paolo Bonzini wrote:
>> 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".  
> Agree. What would be a good way to fix this?

None of what's proposed is fixing the underlying problem of wreckaging

Stop proliferating broken behaviour and please answer the questions I
asked several times now:

   1) Why has the TSC has to restart at the same value?

   2) What is the technical argument that it is correct and acceptable
      to wreckage CLOCK_REALTIME by doing #1?



Powered by blists - more mailing lists