From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH 11/32] KVM: MIPS: Add VZ capability Date: Thu, 2 Mar 2017 11:59:28 +0100 Message-ID: References: <17827db14f848b69e8184ae80b5d63ba01b4b106.1488447004.git-series.james.hogan@imgtec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , Ralf Baechle , Jonathan Corbet , linux-doc@vger.kernel.org To: James Hogan , linux-mips@linux-mips.org, kvm@vger.kernel.org Return-path: In-Reply-To: <17827db14f848b69e8184ae80b5d63ba01b4b106.1488447004.git-series.james.hogan@imgtec.com> Sender: linux-doc-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 02/03/2017 10:36, James Hogan wrote: > - KVM_VM_MIPS_DEFAULT = 2 > > This will provide the best available KVM implementation (even on > older kernels), preferring hardware assisted virtualization over trap > & emulate. The KVM_CAP_MIPS_VZ capability should always be checked > against known values to determine what type of implementation was > chosen. > > This is designed to allow the desired implementation (T&E vs VZ) to be > potentially chosen at runtime rather than being fixed in the kernel > configuration. Can the same kernel run on both TE and VZ? If not, I'm not sure that KVM_VM_MIPS_DEFAULT is a good idea. Paolo