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

2017-12-11 Thread Paolo Bonzini
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

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

2017-12-11 Thread Paolo Bonzini
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

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

2017-12-08 Thread Sironi, Filippo
> On 27. Nov 2017, at 14:09, Steve Rutherford wrote: > > On Mon, Nov 27, 2017 at 3:58 AM, Paolo Bonzini wrote: >> On 26/11/2017 17:41, Filippo Sironi wrote: >>> ... that the guest should see. >>> Guest operating systems may check the microcode

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

2017-12-08 Thread Sironi, Filippo
> On 27. Nov 2017, at 14:09, Steve Rutherford wrote: > > On Mon, Nov 27, 2017 at 3:58 AM, Paolo Bonzini wrote: >> On 26/11/2017 17:41, Filippo Sironi wrote: >>> ... that the guest should see. >>> Guest operating systems may check the microcode version to decide whether >>> to disable certain

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

2017-12-08 Thread Sironi, Filippo
> On 27. Nov 2017, at 03:58, Paolo Bonzini wrote: > > On 26/11/2017 17:41, Filippo Sironi wrote: >> ... that the guest should see. >> Guest operating systems may check the microcode version to decide whether >> to disable certain features that are known to be buggy up to

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

2017-12-08 Thread Sironi, Filippo
> On 27. Nov 2017, at 03:58, Paolo Bonzini wrote: > > On 26/11/2017 17:41, Filippo Sironi wrote: >> ... that the guest should see. >> Guest operating systems may check the microcode version to decide whether >> to disable certain features that are known to be buggy up to certain >> microcode

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

2017-12-08 Thread Sironi, Filippo
> On 27. Nov 2017, at 02:40, Paolo Bonzini wrote: > > On 26/11/2017 17:41, Filippo Sironi wrote: >> ... that the guest should see. >> Guest operating systems may check the microcode version to decide whether >> to disable certain features that are known to be buggy up to

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

2017-12-08 Thread Sironi, Filippo
> On 27. Nov 2017, at 02:40, Paolo Bonzini wrote: > > On 26/11/2017 17:41, Filippo Sironi wrote: >> ... that the guest should see. >> Guest operating systems may check the microcode version to decide whether >> to disable certain features that are known to be buggy up to certain >> microcode

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

2017-12-08 Thread Sironi, Filippo
> On 26. Nov 2017, at 17:02, Wanpeng Li wrote: > > 2017-11-27 0:41 GMT+08:00 Filippo Sironi : >> ... that the guest should see. >> Guest operating systems may check the microcode version to decide whether >> to disable certain features that are known to be

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

2017-12-08 Thread Sironi, Filippo
> On 26. Nov 2017, at 17:02, Wanpeng Li wrote: > > 2017-11-27 0:41 GMT+08:00 Filippo Sironi : >> ... that the guest should see. >> Guest operating systems may check the microcode version to decide whether >> to disable certain features that are known to be buggy up to certain >> microcode

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

2017-11-27 Thread Steve Rutherford
On Mon, Nov 27, 2017 at 3:58 AM, Paolo Bonzini wrote: > On 26/11/2017 17:41, Filippo Sironi wrote: >> ... that the guest should see. >> Guest operating systems may check the microcode version to decide whether >> to disable certain features that are known to be buggy up to

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

2017-11-27 Thread Steve Rutherford
On Mon, Nov 27, 2017 at 3:58 AM, Paolo Bonzini wrote: > On 26/11/2017 17:41, Filippo Sironi wrote: >> ... that the guest should see. >> Guest operating systems may check the microcode version to decide whether >> to disable certain features that are known to be buggy up to certain >> microcode

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

2017-11-27 Thread Paolo Bonzini
On 26/11/2017 17:41, Filippo Sironi wrote: > ... that the guest should see. > Guest operating systems may check the microcode version to decide whether > to disable certain features that are known to be buggy up to certain > microcode versions. Address the issue by making the microcode version >

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

2017-11-27 Thread Paolo Bonzini
On 26/11/2017 17:41, Filippo Sironi wrote: > ... that the guest should see. > Guest operating systems may check the microcode version to decide whether > to disable certain features that are known to be buggy up to certain > microcode versions. Address the issue by making the microcode version >

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

2017-11-27 Thread Paolo Bonzini
On 26/11/2017 17:41, Filippo Sironi wrote: > ... that the guest should see. > Guest operating systems may check the microcode version to decide whether > to disable certain features that are known to be buggy up to certain > microcode versions. Address the issue by making the microcode version >

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

2017-11-27 Thread Paolo Bonzini
On 26/11/2017 17:41, Filippo Sironi wrote: > ... that the guest should see. > Guest operating systems may check the microcode version to decide whether > to disable certain features that are known to be buggy up to certain > microcode versions. Address the issue by making the microcode version >

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

2017-11-26 Thread Wanpeng Li
2017-11-27 0:41 GMT+08:00 Filippo Sironi : > ... that the guest should see. > Guest operating systems may check the microcode version to decide whether > to disable certain features that are known to be buggy up to certain > microcode versions. Address the issue by making the

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

2017-11-26 Thread Wanpeng Li
2017-11-27 0:41 GMT+08:00 Filippo Sironi : > ... that the guest should see. > Guest operating systems may check the microcode version to decide whether > to disable certain features that are known to be buggy up to certain > microcode versions. Address the issue by making the microcode version >

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

2017-11-26 Thread Filippo Sironi
... that the guest should see. Guest operating systems may check the microcode version to decide whether to disable certain features that are known to be buggy up to certain microcode versions. Address the issue by making the microcode version that the guest should see settable. The rationale for

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

2017-11-26 Thread Filippo Sironi
... that the guest should see. Guest operating systems may check the microcode version to decide whether to disable certain features that are known to be buggy up to certain microcode versions. Address the issue by making the microcode version that the guest should see settable. The rationale for