Re: [PATCH RFC] KVM: VMX: drop vmm_exclusive module parameter

2017-06-21 Thread Radim Krčmář
2017-06-21 14:48-0300, Arnaldo Carvalho de Melo: > Em Fri, Mar 10, 2017 at 12:47:13PM +0100, David Hildenbrand escreveu: > > vmm_exclusive=0 leads to KVM setting X86_CR4_VMXE always and calling > > VMXON only when the vcpu is loaded. X86_CR4_VMXE is used as an > > indication in

Re: [PATCH RFC] KVM: VMX: drop vmm_exclusive module parameter

2017-06-21 Thread Radim Krčmář
2017-06-21 14:48-0300, Arnaldo Carvalho de Melo: > Em Fri, Mar 10, 2017 at 12:47:13PM +0100, David Hildenbrand escreveu: > > vmm_exclusive=0 leads to KVM setting X86_CR4_VMXE always and calling > > VMXON only when the vcpu is loaded. X86_CR4_VMXE is used as an > > indication in

Re: [PATCH RFC] KVM: VMX: drop vmm_exclusive module parameter

2017-06-21 Thread Arnaldo Carvalho de Melo
Em Fri, Mar 10, 2017 at 12:47:13PM +0100, David Hildenbrand escreveu: > vmm_exclusive=0 leads to KVM setting X86_CR4_VMXE always and calling > VMXON only when the vcpu is loaded. X86_CR4_VMXE is used as an > indication in cpu_emergency_vmxoff() (called on kdump) if VMXOFF has to be > called. This

Re: [PATCH RFC] KVM: VMX: drop vmm_exclusive module parameter

2017-06-21 Thread Arnaldo Carvalho de Melo
Em Fri, Mar 10, 2017 at 12:47:13PM +0100, David Hildenbrand escreveu: > vmm_exclusive=0 leads to KVM setting X86_CR4_VMXE always and calling > VMXON only when the vcpu is loaded. X86_CR4_VMXE is used as an > indication in cpu_emergency_vmxoff() (called on kdump) if VMXOFF has to be > called. This

Re: [PATCH RFC] KVM: VMX: drop vmm_exclusive module parameter

2017-04-21 Thread Paolo Bonzini
On 10/03/2017 12:47, David Hildenbrand wrote: > vmm_exclusive=0 leads to KVM setting X86_CR4_VMXE always and calling > VMXON only when the vcpu is loaded. X86_CR4_VMXE is used as an > indication in cpu_emergency_vmxoff() (called on kdump) if VMXOFF has to be > called. This is obviously not the

Re: [PATCH RFC] KVM: VMX: drop vmm_exclusive module parameter

2017-04-21 Thread Paolo Bonzini
On 10/03/2017 12:47, David Hildenbrand wrote: > vmm_exclusive=0 leads to KVM setting X86_CR4_VMXE always and calling > VMXON only when the vcpu is loaded. X86_CR4_VMXE is used as an > indication in cpu_emergency_vmxoff() (called on kdump) if VMXOFF has to be > called. This is obviously not the

Re: [PATCH RFC] KVM: VMX: drop vmm_exclusive module parameter

2017-04-18 Thread Paolo Bonzini
On 14/03/2017 21:30, Radim Krčmář wrote: > 2017-03-10 12:47+0100, David Hildenbrand: >> vmm_exclusive=0 leads to KVM setting X86_CR4_VMXE always and calling >> VMXON only when the vcpu is loaded. X86_CR4_VMXE is used as an >> indication in cpu_emergency_vmxoff() (called on kdump) if VMXOFF has

Re: [PATCH RFC] KVM: VMX: drop vmm_exclusive module parameter

2017-04-18 Thread Paolo Bonzini
On 14/03/2017 21:30, Radim Krčmář wrote: > 2017-03-10 12:47+0100, David Hildenbrand: >> vmm_exclusive=0 leads to KVM setting X86_CR4_VMXE always and calling >> VMXON only when the vcpu is loaded. X86_CR4_VMXE is used as an >> indication in cpu_emergency_vmxoff() (called on kdump) if VMXOFF has

Re: [PATCH RFC] KVM: VMX: drop vmm_exclusive module parameter

2017-03-14 Thread Radim Krčmář
2017-03-10 12:47+0100, David Hildenbrand: > vmm_exclusive=0 leads to KVM setting X86_CR4_VMXE always and calling > VMXON only when the vcpu is loaded. X86_CR4_VMXE is used as an > indication in cpu_emergency_vmxoff() (called on kdump) if VMXOFF has to be > called. This is obviously not the case if

Re: [PATCH RFC] KVM: VMX: drop vmm_exclusive module parameter

2017-03-14 Thread Radim Krčmář
2017-03-10 12:47+0100, David Hildenbrand: > vmm_exclusive=0 leads to KVM setting X86_CR4_VMXE always and calling > VMXON only when the vcpu is loaded. X86_CR4_VMXE is used as an > indication in cpu_emergency_vmxoff() (called on kdump) if VMXOFF has to be > called. This is obviously not the case if

[PATCH RFC] KVM: VMX: drop vmm_exclusive module parameter

2017-03-10 Thread David Hildenbrand
vmm_exclusive=0 leads to KVM setting X86_CR4_VMXE always and calling VMXON only when the vcpu is loaded. X86_CR4_VMXE is used as an indication in cpu_emergency_vmxoff() (called on kdump) if VMXOFF has to be called. This is obviously not the case if both are used independtly. Calling VMXOFF without

[PATCH RFC] KVM: VMX: drop vmm_exclusive module parameter

2017-03-10 Thread David Hildenbrand
vmm_exclusive=0 leads to KVM setting X86_CR4_VMXE always and calling VMXON only when the vcpu is loaded. X86_CR4_VMXE is used as an indication in cpu_emergency_vmxoff() (called on kdump) if VMXOFF has to be called. This is obviously not the case if both are used independtly. Calling VMXOFF without