Re: [PATCH v6 5/7] KVM: x86: VMX: Prevent MSR passthrough when MSR access is denied

2020-09-16 Thread Alexander Graf
On 16.09.20 22:13, Aaron Lewis wrote: + /* * These 2 parameters are used to config the controls for Pause-Loop Exiting: * ple_gap:upper bound on the amount of time between two successive @@ -622,6 +642,41 @@ static inline bool report_flexpriority(void) return

Re: [PATCH v6 5/7] KVM: x86: VMX: Prevent MSR passthrough when MSR access is denied

2020-09-16 Thread Aaron Lewis
> > > >> + > >> /* > >>* These 2 parameters are used to config the controls for Pause-Loop > >> Exiting: > >>* ple_gap:upper bound on the amount of time between two successive > >> @@ -622,6 +642,41 @@ static inline bool report_flexpriority(void) > >> return

Re: [PATCH v6 5/7] KVM: x86: VMX: Prevent MSR passthrough when MSR access is denied

2020-09-16 Thread Alexander Graf
On 04.09.20 04:18, Aaron Lewis wrote: +/* + * List of MSRs that can be directly passed to the guest. + * In addition to these x2apic and PT MSRs are handled specially. + */ +static u32 vmx_possible_passthrough_msrs[MAX_POSSIBLE_PASSGHROUGH_MSRS] = { MAX_POSSIBLE_PASSGHROUGH_MSRS should be

Re: [PATCH v6 5/7] KVM: x86: VMX: Prevent MSR passthrough when MSR access is denied

2020-09-03 Thread Aaron Lewis
> +/* > + * List of MSRs that can be directly passed to the guest. > + * In addition to these x2apic and PT MSRs are handled specially. > + */ > +static u32 vmx_possible_passthrough_msrs[MAX_POSSIBLE_PASSGHROUGH_MSRS] = { MAX_POSSIBLE_PASSGHROUGH_MSRS should be MAX_POSSIBLE_PASSTHROUGH_MSRS > +

[PATCH v6 5/7] KVM: x86: VMX: Prevent MSR passthrough when MSR access is denied

2020-09-02 Thread Alexander Graf
We will introduce the concept of MSRs that may not be handled in kernel space soon. Some MSRs are directly passed through to the guest, effectively making them handled by KVM from user space's point of view. This patch introduces all logic required to ensure that MSRs that user space wants