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:   Mon, 11 May 2020 09:11:20 +0800
From:   Xiaoyao Li <>
To:     Andy Lutomirski <>
Cc:     Paolo Bonzini <>,
        Thomas Gleixner <>,
        Sean Christopherson <>,
        kvm list <>,
        LKML <>, X86 ML <>,
        Ingo Molnar <>, Borislav Petkov <>,
        "H. Peter Anvin" <>,
        Peter Zijlstra <>,
        Arvind Sankar <>,
        Tony Luck <>,
        Fenghua Yu <>
Subject: Re: [PATCH v9 8/8] x86/split_lock: Enable split lock detection
 initialization when running as an guest on KVM

On 5/10/2020 1:15 PM, Andy Lutomirski wrote:
> On Fri, May 8, 2020 at 8:04 PM Xiaoyao Li <> wrote:
>> When running as guest, enumerating feature split lock detection through
>> CPU model is not easy since CPU model is configurable by host VMM.
>> If running upon KVM, it can be enumerated through
> This needs crystal clear documentation.  What, exactly, is the host
> telling the guest if it sets this flag?
>> and if KVM_HINTS_SLD_FATAL is set, it
>> needs to be set to sld_fatal mode.
> This needs much better docs.  Do you mean:
> "If KVM_HINTS_SLD_FATAL is set, then the guest will get #AC if it does
> a split-lock regardless of what is written to MSR_TEST_CTRL?"

Hi Andy,

introduced in Patch 5. Do I still need to explain them in detail in this 

Powered by blists - more mailing lists