linux-kernel - Re: [PATCH 2/2] KVM: x86: Allow userspace to define what's the microcode version

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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <fa96ec2b-6538-3a56-5f42-bbf923fc3bde@redhat.com>
Date:   Mon, 11 Dec 2017 17:03:14 +0100
From:   Paolo Bonzini <pbonzini@...hat.com>
To:     "Sironi, Filippo" <sironi@...zon.de>
Cc:     "rkrcmar@...hat.com" <rkrcmar@...hat.com>,
        "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2] KVM: x86: Allow userspace to define what's the
 microcode version

On 09/12/2017 08:42, Sironi, Filippo wrote:
> I wanted to do the work once rather than doing it per vCPU but using
> KVM_{GET|SET}_MSR and extending the list of MSRs that userspace can
> save/restore is certainly doable.
> 
> I'll look into that and post a v2.

Thanks!

Paolo