linux-kernel - Re: [PATCH] KVM: SVM: use vmsave/vmload for saving/restoring additional host state

lists.openwall.net		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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:   Fri, 11 Dec 2020 14:39:12 +0100
From:   Paolo Bonzini <pbonzini@...hat.com>
To:     Michael Roth <michael.roth@....com>,
        Andy Lutomirski <luto@...nel.org>,
        Sean Christopherson <seanjc@...gle.com>
Cc:     kvm list <kvm@...r.kernel.org>,
        Sean Christopherson <sean.j.christopherson@...el.com>,
        Vitaly Kuznetsov <vkuznets@...hat.com>,
        Wanpeng Li <wanpengli@...cent.com>,
        Jim Mattson <jmattson@...gle.com>,
        Joerg Roedel <joro@...tes.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
        X86 ML <x86@...nel.org>, "H.Peter Anvin" <hpa@...or.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Tom Lendacky <thomas.lendacky@....com>
Subject: Re: [PATCH] KVM: SVM: use vmsave/vmload for saving/restoring
 additional host state

On 11/12/20 14:28, Michael Roth wrote:
> Quoting Paolo Bonzini (2020-12-11 05:42:02)
>> On 11/12/20 02:27, Sean Christopherson wrote:
>>> Michael, please reply to all so that everyone can read along and so that the
>>> conversation gets recorded in the various mailing list archives.
>>>
>>> If you are replying all, then I think something funky is going on with AMD's
>>> mail servers, as I'm not getting your responses (I double checked SPAM), nor are
>>> they showing up on lore.
>> I think somebody else reported similar issues with AMD's mail servers.
> It looks like my messages did make their way to lore eventually:
> 
>    https://lore.kernel.org/patchwork/patch/1352128/

Ok, so maybe some graylisting.  If it fixes itself it's not a big deal.

Paolo