linux-kernel - Re: [PATCH 1/4] KVM: VMX: cache secondary exec controls

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

Date:   Thu, 24 Aug 2017 08:41:17 -0700
From:   Jim Mattson <jmattson@...gle.com>
To:     Paolo Bonzini <pbonzini@...hat.com>
Cc:     LKML <linux-kernel@...r.kernel.org>, kvm list <kvm@...r.kernel.org>
Subject: Re: [PATCH 1/4] KVM: VMX: cache secondary exec controls

Userspace can establish the value of the virtualized
IA32_VMX_PROCBASED_CTLS2 MSR via the KVM_SET_MSRS ioctl, which goes
through vms_set_vmx_msr. But maybe that's not important, since
features can only be disabled on that path.

On Thu, Aug 24, 2017 at 8:25 AM, Paolo Bonzini <pbonzini@...hat.com> wrote:
> On 24/08/2017 16:47, Jim Mattson wrote:
>>> Currently, secondary execution controls are divided in three groups:
>>>
>>> - static, depending mostly on the module arguments or the processor
>>>   (vmx_secondary_exec_control)
>>>
>>> - static, depending on CPUID (vmx_cpuid_update)
>> There should also be:
>>
>> - static, depending on guest VMX capability MSRs (vmx_set_vmx_msr)
>
> Can you explain what you mean?
>
> Paolo